Triple

T3828151
Position Surface form Disambiguated ID Type / Status
Subject Tivoli E88741 entity
Predicate hasAncientName P20952 FINISHED
Object Tibur E199555 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: Tibur | Statement: [Tivoli, hasAncientName, Tibur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tibur
Context triple: [Tivoli, hasAncientName, 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. 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.
  • C. Tura
    Tura is a district in southern Cairo, Egypt, historically known for its limestone quarries used in ancient Egyptian monuments.
  • D. MinMinas
    MinMinas is the abbreviated name of Colombia’s Ministry of Mines and Energy, the government body responsible for national policies on mining and energy resources.
  • E. Tain
    Tain is a historic town in the Highlands of Scotland, known as one of the country’s oldest royal burghs and a regional administrative and judicial center.
  • 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_69aed9538cf881909d9ce8ca4ac7c18c completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeeb66c0bc819084d9a9fe32e8433a completed March 9, 2026, 3:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69b503f9df8c8190b42c544e827d6c76 completed March 14, 2026, 6:45 a.m.
Created at: March 9, 2026, 3:17 p.m.