Triple
T2098762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scribonia |
E37043
|
entity |
| Predicate | spouseOrderInAugustusLife |
P4764
|
FINISHED |
| Object | second wife |
—
|
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: second wife | Statement: [Scribonia, spouseOrderInAugustusLife, second wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOrderInAugustusLife Context triple: [Scribonia, spouseOrderInAugustusLife, second wife]
-
A.
spouseOrder
chosen
Indicates the position or sequence of a person among multiple spouses in a marital relationship.
-
B.
spouseDynasty
Indicates that there is a marital relationship linking an entity to the dynasty (family line or ruling house) of their spouse.
-
C.
predecessorAsEasternAugustus
Indicates that one entity previously held the position of Eastern Roman Emperor immediately before the other entity.
-
D.
successorAsEasternAugustus
Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
-
E.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba9de75c81909770409b5ae62c24 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.