Triple
T37499882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 255 |
E931926
|
entity |
| Predicate | formsPartialLoopWith |
P103593
|
FINISHED |
| Object | Interstate 270 |
—
|
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 270 | Statement: [Interstate 255, formsPartialLoopWith, Interstate 270]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPartialLoopWith Context triple: [Interstate 255, formsPartialLoopWith, Interstate 270]
-
A.
formsLoopWith
Indicates that two or more entities are connected in such a way that they form a closed cycle or loop with one another.
-
B.
formsLoopFrom
Indicates that something creates or constitutes a closed path or cycle originating from a specified starting point.
-
C.
formsLoopAround
Indicates that one entity extends or curves so as to create a closed loop encircling or surrounding another entity or region.
-
D.
partOfLoopWith
chosen
Indicates that one entity participates as a component or segment within the same loop structure as another entity.
-
E.
isLoopOf
Indicates that one entity represents a loop or cyclic structure corresponding to, derived from, or associated with another entity.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 3, 2026, 4:17 p.m.