Triple
T36805946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergius Saranoff |
E909450
|
entity |
| Predicate | laterEngagedTo |
P202802
|
FINISHED |
| Object | Louka |
—
|
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: Louka | Statement: [Sergius Saranoff, laterEngagedTo, Louka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterEngagedTo Context triple: [Sergius Saranoff, laterEngagedTo, Louka]
-
A.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
B.
initiallyEngagedTo
Indicates that one entity was first formally promised or committed to marry another entity at the beginning of a specified time or event.
-
C.
secretlyEngagedTo
Indicates that one person is engaged to marry another, but this engagement is intentionally kept hidden from others.
-
D.
engagedOn
Indicates that two entities are committed to be married to each other as of a specific date or point in time.
-
E.
engagedOnDate
Indicates that two entities entered into an engagement or formal commitment on a specific calendar date.
- F. None of above. chosen
Provenance (4 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_6a00bc06bf3081908973b6c05797299f |
completed | May 10, 2026, 5:10 p.m. |
Created at: May 3, 2026, 4:12 p.m.