Triple
T31537381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donna W. Scott |
E804643
|
entity |
| Predicate | notableRelativeByMarriageOccupation |
P115507
|
FINISHED |
| Object | film director |
—
|
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: film director | Statement: [Donna W. Scott, notableRelativeByMarriageOccupation, film director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRelativeByMarriageOccupation Context triple: [Donna W. Scott, notableRelativeByMarriageOccupation, film director]
-
A.
notable relative occupation
chosen
Indicates that a person has a relative whose occupation is notable or significant in some recognized way.
-
B.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
C.
spouseNotableAncestor
Indicates that a person’s spouse has an ancestor who is notable or historically significant.
-
D.
notableRelativeType
Indicates the specific familial or relational role that a notable relative has in relation to the subject.
-
E.
notableFamilyFor
Indicates that a family is particularly recognized or distinguished for a specific person, achievement, role, or characteristic.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:04 p.m.