Triple
T590388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Traitorous Eight |
E17253
|
entity |
| Predicate | reasonForLeaving |
P15987
|
FINISHED |
| Object | disagreements with William Shockley |
—
|
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: disagreements with William Shockley | Statement: [Traitorous Eight, reasonForLeaving, disagreements with William Shockley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForLeaving Context triple: [Traitorous Eight, reasonForLeaving, disagreements with William Shockley]
-
A.
reasonForWithdrawal
Indicates the cause, motive, or circumstance that explains why a withdrawal occurred.
-
B.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
C.
reasonForDiscontinuation
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
D.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
E.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985ada988190aaea628a9b55bca4 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.