Triple
T25101400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willis Davidge |
E628733
|
entity |
| Predicate | formerAttitude |
P146400
|
FINISHED |
| Object | prejudiced against Dracs |
—
|
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: prejudiced against Dracs | Statement: [Willis Davidge, formerAttitude, prejudiced against Dracs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAttitude Context triple: [Willis Davidge, formerAttitude, prejudiced against Dracs]
-
A.
finalAttitude
Indicates the ultimate stance, feeling, or evaluative judgment one entity holds toward another entity or situation after a process or interaction has concluded.
-
B.
former
chosen
Indicates that an entity previously held a role, status, or relationship but no longer does so in the present.
-
C.
formerPart
Indicates that an entity was once a component or member of another entity but is no longer part of it.
-
D.
initialAttitude
Indicates the starting stance, feeling, or disposition one entity holds toward another or toward a situation before any interaction or change occurs.
-
E.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:25 a.m.