Triple
T34970924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metairie Ridge |
E1008534
|
entity |
| Predicate | transportationAxisFor |
P190575
|
FINISHED |
| Object | Metairie Road corridor |
—
|
NE NERFINISHED |
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: Metairie Road corridor | Statement: [Metairie Ridge, transportationAxisFor, Metairie Road corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportationAxisFor Context triple: [Metairie Ridge, transportationAxisFor, Metairie Road corridor]
-
A.
isTransportationAxisOf
chosen
Indicates that one entity serves as a primary route or corridor used to transport or move another entity from place to place.
-
B.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
C.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
D.
isMajorTransportAxisIn
Indicates that a route or corridor functions as a primary or heavily used transportation pathway within a specified area or region.
-
E.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
- F. None of above.
Provenance (3 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:01 p.m.