Triple
T29595411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ippolit |
E754278
|
entity |
| Predicate | romanticStatusAtBeginning |
P82370
|
FINISHED |
| Object | engaged |
—
|
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: engaged | Statement: [Ippolit, romanticStatusAtBeginning, engaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticStatusAtBeginning Context triple: [Ippolit, romanticStatusAtBeginning, engaged]
-
A.
romanticRelationshipStatus
chosen
Indicates the nature or state of a romantic relationship between entities, such as whether they are dating, committed, separated, or otherwise romantically involved.
-
B.
neverMarried
Indicates that the subject has not been legally married to any partner at any time up to the present.
-
C.
formerRelationshipStatus
Indicates that a relationship between entities existed in the past but no longer holds in the present.
-
D.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
E.
spouseStatusAtMarriage
Indicates the marital status each partner held at the time their marriage to one another was formed.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 6:17 p.m.