Triple
T30067150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 264 (Kentucky) |
E764064
|
entity |
| Predicate | isLoopOf |
P168407
|
FINISHED |
| Object | Interstate 64 |
—
|
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: Interstate 64 | Statement: [Interstate 264 (Kentucky), isLoopOf, Interstate 64]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLoopOf Context triple: [Interstate 264 (Kentucky), isLoopOf, Interstate 64]
-
A.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
B.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
C.
isLoopFree
Indicates that the structure or process has no cycles, repetitions, or self-referential paths.
-
D.
hasLoopMode
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
-
E.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ca767788190abd71ea33ce049e5 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:59 p.m.