Triple
T14520859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespasia |
E340644
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Vespasia |
E342378
|
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: Vespasia | Statement: [Vespasia, familyName, Vespasia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vespasia Context triple: [Vespasia, familyName, Vespasia]
-
A.
Vespasia
chosen
Vespasia was an ancient Roman family name associated with the noble lineage of the Vespasii, relatives of the emperor Vespasian.
-
B.
Mucia
Mucia was an ancient Roman noble family (gens) to which the patrician Mucia Tertia belonged.
-
C.
Statilia
Statilia is an ancient Roman feminine praenomen (given name) most notably borne by the empress Statilia Messalina, wife of Emperor Nero.
-
D.
Maenza
Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
-
E.
Eraclea
Eraclea is a small coastal town in northeastern Italy known for its beaches along the Adriatic Sea and its proximity to Venice.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a72cff08190878b4bed9b0b5eb5 |
completed | April 14, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a4b71688190ae9ebccdc81d09f8 |
completed | May 8, 2026, 5:53 a.m. |
Created at: April 10, 2026, 1:22 a.m.