Triple
T30161994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mucia Tertia |
E766690
|
entity |
| Predicate | marriageToPompeyEndApprox |
P86431
|
FINISHED |
| Object | circa 61 BC |
—
|
LITERAL 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: circa 61 BC | Statement: [Mucia Tertia, marriageToPompeyEndApprox, circa 61 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marriageToPompeyEndApprox Context triple: [Mucia Tertia, marriageToPompeyEndApprox, circa 61 BC]
-
A.
marriageEndToPompey
chosen
Indicates that a marriage concluded or was terminated in relation to Pompey (e.g., by divorce, annulment, or death).
-
B.
marriageStartToPompey
Indicates the point in time or event at which a marriage to Pompey begins.
-
C.
marriageEndWithPompey
Indicates that a marriage concludes or is terminated through association with Pompey (e.g., by marrying or being married to Pompey).
-
D.
endTime (marriage to Nero)
Indicates the point in time at which the marriage to Nero concluded or was terminated.
-
E.
marriageStartWithPompey
Indicates the point in time or event at which a marriage involving Pompey begins.
- F. None of above.
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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 7:22 p.m.