Triple
T34868079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrett family |
E1005068
|
entity |
| Predicate | resultOfCentralEvent |
P59870
|
FINISHED |
| Object | Elizabeth’s estrangement from her father |
—
|
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: Elizabeth’s estrangement from her father | Statement: [Barrett family, resultOfCentralEvent, Elizabeth’s estrangement from her father]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfCentralEvent Context triple: [Barrett family, resultOfCentralEvent, Elizabeth’s estrangement from her father]
-
A.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
isCulminatingEventOf
Indicates that an event represents the final or peak outcome within a larger process, sequence, or series of related events.
-
C.
resultOfEmergency
Indicates that something occurs or exists as a direct consequence of an emergency situation or event.
-
D.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
eventResult
Indicates that one event occurs as a consequence or outcome of another event.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: May 3, 2026, 4 p.m.