Triple
T31343356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Highway 33 |
E799370
|
entity |
| Predicate | terminusSouthParish |
P179521
|
FINISHED |
| Object | Lincoln Parish, Louisiana |
—
|
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: Lincoln Parish, Louisiana | Statement: [Louisiana Highway 33, terminusSouthParish, Lincoln Parish, Louisiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusSouthParish Context triple: [Louisiana Highway 33, terminusSouthParish, Lincoln Parish, Louisiana]
-
A.
terminusSouthState
Indicates that the southern endpoint or terminus of an entity (such as a route or line) is located in a specified state.
-
B.
terminusSouthNear
Indicates that the southern end or terminus of one entity is located close to another entity.
-
C.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
D.
terminusSouthCountry
Indicates that the southern terminus of a route, line, or connection is located within the specified country.
-
E.
terminusSouthConnection
Indicates a connection where one entity serves as the southern terminus or endpoint of another entity.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 29, 2026, 9:17 p.m.