Triple
T13820567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peraea |
E332123
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Livias |
E332121
|
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: Livias | Statement: [Peraea, capital, Livias]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Livias Context triple: [Peraea, capital, Livias]
-
A.
Livias
chosen
Livias was an ancient town in the region of Perea, east of the Jordan River, known from classical and biblical-era sources.
-
B.
Celso
Celso is a small village in southern Italy that serves as a frazione (hamlet) of the municipality of Pollica in the Campania region.
-
C.
Lucio
Lucio is a roguish, witty gentleman in Shakespeare’s play "Measure for Measure," known for his bawdy humor, moral hypocrisy, and role as a comic commentator on the play’s themes of justice and corruption.
-
D.
Lucio
Lucio is a popular support hero in the game Overwatch, known for his music-based abilities that heal and speed up teammates.
-
E.
Lucio
Lucio is an Italian given name commonly used for men, derived from the Latin name Lucius meaning "light."
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0282d4d08190b754cda7683408c4 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b8e41f448190baabfd06d78b45b7 |
completed | May 3, 2026, 9:06 p.m. |
Created at: April 9, 2026, 10:12 p.m.