Triple
T13208358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brickell Loop |
E314422
|
entity |
| Predicate | connectsWith |
P37
|
FINISHED |
| Object | Omni Loop |
E312103
|
NE 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: Omni Loop | Statement: [Brickell Loop, connectsWith, Omni Loop]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Omni Loop Context triple: [Brickell Loop, connectsWith, Omni Loop]
-
A.
Omni Loop
chosen
Omni Loop is one of the downtown Miami Metromover’s automated people-mover loops that circulates through the Omni district and nearby areas.
-
B.
Euroloop
Euroloop is a trackside transmission system used in the European Train Control System to continuously send data to passing trains and enhance signaling reliability and safety.
-
C.
A Loop
A Loop is a modern streetcar route in Portland, Oregon, that provides circulator service through the central city and adjacent neighborhoods as part of the Portland Streetcar system.
-
D.
Loopt
Loopt was an early location-based social networking mobile app startup that allowed users to share their real-time location with friends.
-
E.
Omni
Omni is a short book in the Book of Mormon that continues the historical and spiritual record of the Nephite people through a series of brief entries by multiple authors.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9cb7ac819095cff8699993c419 |
completed | April 10, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f611b11c8190b9f89313eb2b5fab |
completed | May 3, 2026, 7:15 a.m. |
Created at: April 9, 2026, 9:17 p.m.