Triple
T14896154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddie C. Thomas |
E359880
|
entity |
| Predicate | workplaceObjection |
P926
|
FINISHED |
| Object | production of armaments |
—
|
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: production of armaments | Statement: [Eddie C. Thomas, workplaceObjection, production of armaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workplaceObjection Context triple: [Eddie C. Thomas, workplaceObjection, production of armaments]
-
A.
workProhibited
Indicates that an entity is not allowed or is forbidden to perform a particular work or job activity.
-
B.
workConditions
Indicates the terms, environment, and circumstances under which work or a job is performed.
-
C.
laborRelationsIssue
chosen
Indicates a relationship where there is a dispute, concern, or matter involving labor relations between workers (or their representatives) and employers.
-
D.
employment
Indicates a relationship where one entity hires, contracts, or otherwise engages another to perform work or services, typically in exchange for compensation.
-
E.
workplaceAtTimeOfAttack
Indicates that the specified location was the person’s workplace at the time the attack occurred.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6070b248190be8f4f91a0c0b1f3 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.