Triple

T10446349
Position Surface form Disambiguated ID Type / Status
Subject Laurentius E246297 entity
Predicate associatedWith P37 FINISHED
Object Laurentum E468400 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: Laurentum | Statement: [Laurentius, associatedWith, Laurentum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laurentum
Context triple: [Laurentius, associatedWith, Laurentum]
  • A. Laurentum chosen
    Laurentum was an ancient coastal city in Latium, traditionally associated with the legendary king Latinus and early Roman mythic history.
  • B. Asculum
    Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
  • C. Maenza
    Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
  • D. Lauriacum
    Lauriacum was a major Roman military and administrative center in the province of Noricum, located near the Danube in what is now Austria.
  • E. Falciano
    Falciano is a village and civil parish in the Republic of San Marino, forming part of the municipality of Serravalle.
  • 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_69d381c04fe08190957c26c526a3b05a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4fdc0520c819098d2d53ee46a89ae completed April 7, 2026, 12:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69d89fa5b3b081909af7de1745372add completed April 10, 2026, 6:58 a.m.
Created at: April 6, 2026, 12:16 p.m.