Triple
T10821628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domitia Longina |
E255383
|
entity |
| Predicate | positionHeld |
P8
|
FINISHED |
| Object | Augusta |
E196016
|
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: Augusta | Statement: [Domitia Longina, positionHeld, Augusta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Augusta Context triple: [Domitia Longina, positionHeld, Augusta]
-
A.
Augusta
Augusta is the given first name of Ada Lovelace, the 19th-century mathematician often regarded as the world's first computer programmer.
-
B.
Augusta
Augusta is a rural township in eastern Ontario, Canada, located along the St. Lawrence River in the United Counties of Leeds and Grenville.
-
C.
Augusta
Augusta is the first name of Lady Gregory, the influential Irish dramatist, folklorist, and co-founder of Dublin’s Abbey Theatre.
-
D.
Augusta
chosen
Augusta was an honorific title used for empresses and other high-ranking women in the Roman and Byzantine Empires, signifying imperial dignity and status.
-
E.
Augusta
Augusta is a small coastal town in the far southwest of Western Australia, known for its scenic coastline, proximity to Cape Leeuwin, and role as a popular tourist and fishing destination.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344ae2688190bceabf41c79d298d |
completed | April 9, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de8578428c8190a25d9008881d0114 |
completed | April 14, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:18 p.m.