Triple
T37772324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | south-central Nevada |
E941583
|
entity |
| Predicate | hasNotableSettlementNearby |
P3883
|
FINISHED |
| Object | Rachel, Nevada |
E277993
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Rachel, Nevada | Statement: [south-central Nevada, hasNotableSettlementNearby, Rachel, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSettlementNearby Context triple: [south-central Nevada, hasNotableSettlementNearby, Rachel, Nevada]
-
A.
hasNearestLargerSettlement
Indicates that one settlement is associated with the geographically closest settlement that is larger in size or population.
-
B.
hasNotableSettlementRegion
Indicates that an entity has a significant or well-known settlement located within a specified geographic region.
-
C.
hasNearbyCoastalSettlement
Indicates that one entity has a coastal settlement located in close geographic proximity to it.
-
D.
hasNearbySettlementPattern
Indicates that one entity exhibits a settlement distribution or layout that is spatially close to, or clustered around, another entity.
-
E.
hasNearbyTown
chosen
Indicates that one location has a town situated close to it in geographic proximity.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4117dd215c81909d412082440d7d09 |
completed | June 28, 2026, 12:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.