Triple
T28035321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariana |
E708388
|
entity |
| Predicate | endsUpMarriedTo |
P137120
|
FINISHED |
| Object | Angelo |
—
|
NE NERFINISHED |
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: Angelo | Statement: [Mariana, endsUpMarriedTo, Angelo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsUpMarriedTo Context triple: [Mariana, endsUpMarriedTo, Angelo]
-
A.
resultedInMarriageTo
chosen
Indicates that one event, action, or circumstance led to or caused a marriage to occur between the related entities.
-
B.
marriesFor
Indicates that one entity enters into marriage with another entity specifically for a particular reason, motive, or benefit.
-
C.
marriedBy
Indicates that one entity is the officiant or authority who performs and formalizes the marriage of another entity.
-
D.
elevatedByMarriageTo
Indicates that one entity attains a higher social, legal, or status position as a direct result of marrying another entity.
-
E.
isFianceeOf
Indicates that one person is the engaged-to-be-married partner of another person.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63c76fa1c81909070bd8352404f26 |
completed | May 2, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:20 p.m.