Triple
T16389345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doc Burton |
E398007
|
entity |
| Predicate | viewsOnConflict |
P123227
|
FINISHED |
| Object | treats strike as social experiment |
—
|
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: treats strike as social experiment | Statement: [Doc Burton, viewsOnConflict, treats strike as social experiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsOnConflict Context triple: [Doc Burton, viewsOnConflict, treats strike as social experiment]
-
A.
viewOnAmbiguity
Indicates an entity’s stance or attitude toward ambiguity, such as how much uncertainty or vagueness it accepts or prefers.
-
B.
viewOnCompromise
Indicates a stance or perspective that an entity holds regarding the acceptability, terms, or implications of making a compromise.
-
C.
basedOnConflict
Indicates that one entity is derived from, influenced by, or structured around a particular conflict involving another entity.
-
D.
viewOnUnions
Indicates a person's stance, opinion, or attitude toward labor unions or unionization.
-
E.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326414f44819093ebc11f1b63444c |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.