Triple
T33797426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheila Birling |
E866112
|
entity |
| Predicate | engagementStatusAtStart |
P177715
|
FINISHED |
| Object | recently engaged to Gerald Croft |
—
|
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: recently engaged to Gerald Croft | Statement: [Sheila Birling, engagementStatusAtStart, recently engaged to Gerald Croft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementStatusAtStart Context triple: [Sheila Birling, engagementStatusAtStart, recently engaged to Gerald Croft]
-
A.
engagementStatusWith
Indicates the current state or condition of an ongoing or potential engagement or interaction between two entities.
-
B.
engagedAt
Indicates that two entities became formally engaged to be married at a specific time or event.
-
C.
engagementStart
Indicates the point in time or event at which an engagement, interaction, or formal involvement between parties begins.
-
D.
engagedOn
Indicates that two entities are committed to be married to each other as of a specific date or point in time.
-
E.
engagedBy
Indicates that an entity is actively involved, occupied, or participating in an activity, process, or interaction initiated or provided by another entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.