Triple
T17441100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oak Alley Plantation |
E424652
|
entity |
| Predicate | treeAvenueLength |
P127462
|
FINISHED |
| Object | approximately 800 feet |
—
|
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: approximately 800 feet | Statement: [Oak Alley Plantation, treeAvenueLength, approximately 800 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treeAvenueLength Context triple: [Oak Alley Plantation, treeAvenueLength, approximately 800 feet]
-
A.
roadLength
Indicates the measured distance or extent of a road, typically expressed in units of length.
-
B.
avenueOfOaksPlantedBetween
Indicates that a line or avenue of oak trees has been planted between two specified locations or features.
-
C.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
-
D.
hasTreeLinedStreets
Indicates that the streets in a given area are lined or bordered with trees along their sides.
-
E.
isNumberedAvenueOf
Indicates that one entity is an avenue identified by a numerical designation that belongs to or is part of the other entity (such as a city or road network).
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff75538819083f77756d39a1aaa |
completed | April 19, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.