Triple
T31538328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Beltway |
E804670
|
entity |
| Predicate | loopRole |
P171945
|
FINISHED |
| Object | forms part of full circumferential loop around Jacksonville |
—
|
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: forms part of full circumferential loop around Jacksonville | Statement: [East Beltway, loopRole, forms part of full circumferential loop around Jacksonville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopRole Context triple: [East Beltway, loopRole, forms part of full circumferential loop around Jacksonville]
-
A.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
B.
roleInFrame
Indicates that an entity participates in a specific semantic frame by filling a particular role within that frame.
-
C.
roleInLap
Indicates the specific function or position an entity holds during a particular lap within a sequence of laps.
-
D.
roleInTheVoices
Indicates that an entity has a specific role or participation in the production or performance of "The Voices."
-
E.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:04 p.m.