Triple
T31173042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Swan |
E794664
|
entity |
| Predicate | encountersMissedFrom |
P162421
|
FINISHED |
| Object | a wealthy couple seeking an heir |
—
|
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: a wealthy couple seeking an heir | Statement: [David Swan, encountersMissedFrom, a wealthy couple seeking an heir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encountersMissedFrom Context triple: [David Swan, encountersMissedFrom, a wealthy couple seeking an heir]
-
A.
ifDayMissed
Indicates that a specified condition or consequence applies when a particular day has been missed.
-
B.
encountersDoctor
chosen
Indicates that one entity comes into contact with or meets a doctor in some context or situation.
-
C.
missedSeason
Indicates that an entity did not participate in or was absent for a particular season of an activity, event, or series.
-
D.
wentMissingOn
Indicates that an entity disappeared or became unaccounted for starting on a specific date or time.
-
E.
associatedWithMissal
Indicates a relationship where something is connected or linked to a particular missal, such as being derived from, contained in, or used together with that missal.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.