Triple
T25295063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isobel Harrison |
E634193
|
entity |
| Predicate | spouse notableWork |
P161452
|
FINISHED |
| Object | The Planets |
—
|
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: The Planets | Statement: [Isobel Harrison, spouse notableWork, The Planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouse notableWork Context triple: [Isobel Harrison, spouse notableWork, The Planets]
-
A.
spouseNotableFor
Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
spouseNotableWorkField
Indicates that the notable work or professional field associated with a person’s spouse is being specified.
-
C.
spouseNotableWorkLanguage
Indicates that the notable work of a person's spouse is expressed or created in a particular language.
-
D.
spouseNotableAward
Indicates that a person’s spouse has received a notable award or honor.
-
E.
spouseOfNotableEvent
Indicates a marital relationship where one spouse is a notable event or is contextually defined through association with a notable event.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f613bc641c819084343cc78d080640 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f613502d808190b89927e5e734b43a |
completed | May 2, 2026, 3:08 p.m. |
Created at: April 21, 2026, 1:22 p.m.