Triple
T22904708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Tiburtina |
E568413
|
entity |
| Predicate | terminusB |
P388
|
FINISHED |
| Object | Tibur |
—
|
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: Tibur | Statement: [Via Tiburtina, terminusB, Tibur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tibur Context triple: [Via Tiburtina, terminusB, Tibur]
-
A.
Tibur
chosen
Tibur is the ancient Roman town in Latium, now known as Tivoli, famed for its villas and temples east of Rome.
-
B.
Toron
Toron was a medieval lordship and fortress in the Crusader Kingdom of Jerusalem, located in what is now southern Lebanon.
-
C.
Tura
Tura is a remote urban-type settlement in central Siberia, Russia, historically serving as an administrative center in the Evenk region.
-
D.
Tura
Tura is a prominent town in the Indian state of Meghalaya, serving as a major administrative, cultural, and economic center in the Garo Hills region.
-
E.
Tura
Tura is a district in southern Cairo, Egypt, historically known for its limestone quarries used in ancient Egyptian monuments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458cd9e48190943ad2e34485d939 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801895f48190bb8d49a41feac7ef |
completed | April 29, 2026, 3:50 a.m. |
Created at: April 17, 2026, 3:41 p.m.