Triple
T30598477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Clark Terrell |
E778846
|
entity |
| Predicate | resistedControlBy |
P167077
|
FINISHED |
| Object | turning phaser on himself |
—
|
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: turning phaser on himself | Statement: [Captain Clark Terrell, resistedControlBy, turning phaser on himself]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resistedControlBy Context triple: [Captain Clark Terrell, resistedControlBy, turning phaser on himself]
-
A.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
resistedUntil
Indicates that an entity continued to oppose or withstand another entity or force up to a specific point in time or event.
-
C.
opposedControlBy
chosen
Indicates that one entity resists, challenges, or acts against the control or authority exerted by another entity.
-
D.
resistedUnderLeader
Indicates that an entity engaged in resistance or opposition while being directed or led by a specified leader.
-
E.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b01d7c819083ccc732d66d4d33 |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:25 p.m.