Triple
T9092702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise Valley, Arizona |
E217928
|
entity |
| Predicate | transportationReliance |
P87132
|
FINISHED |
| Object | automobile-oriented |
—
|
LITERAL 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: automobile-oriented | Statement: [Paradise Valley, Arizona, transportationReliance, automobile-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationReliance Context triple: [Paradise Valley, Arizona, transportationReliance, automobile-oriented]
-
A.
transportationReference
Indicates that one entity serves as a reference or identifier for a specific mode, instance, or detail of transportation associated with another entity.
-
B.
transportation
Indicates the movement of someone or something from one place to another, typically using a vehicle or transit system.
-
C.
transportReliability
Indicates how consistently and dependably a transport service or system performs as expected over time.
-
D.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- F. None of above. chosen
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_69ca83d8ab5881909d8fddae363b32b1 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc96b18b24819097b525ddad3a85c0 |
completed | April 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:14 p.m.