Triple
T12427130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Highway 540 |
E296926
|
entity |
| Predicate | isPartiallyCompletedLoop |
P45410
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [North Carolina Highway 540, isPartiallyCompletedLoop, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartiallyCompletedLoop Context triple: [North Carolina Highway 540, isPartiallyCompletedLoop, yes]
-
A.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
B.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
C.
partiallyCompleted
chosen
Indicates that an action, process, or task has been started and progressed to some extent, but has not yet been fully completed.
-
D.
partOfLoopWith
Indicates that one entity participates as a component or segment within the same loop structure as another entity.
-
E.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94df948308190ace333230a4a3b38 |
completed | April 10, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69d94d391c548190996a8c698357f273 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.