Triple
T9370592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornelia Metella |
E225519
|
entity |
| Predicate | spouseMarriageEvent |
P85988
|
FINISHED |
| Object | marriage to Pompey the Great in 52 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: marriage to Pompey the Great in 52 BC | Statement: [Cornelia Metella, spouseMarriageEvent, marriage to Pompey the Great in 52 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseMarriageEvent Context triple: [Cornelia Metella, spouseMarriageEvent, marriage to Pompey the Great in 52 BC]
-
A.
spouseAtEvent
Indicates that two individuals are spouses who are present together at a specific event.
-
B.
hasSpouseNotableEvent
chosen
Indicates that a person’s spouse is associated with a notable event related to that person.
-
C.
spouseAssociatedWith
Indicates a marital or spousal relationship or close association between two entities.
-
D.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
-
E.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd508274d88190a64b79ab731ac6a1 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.