Triple
T11984788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Teavee |
E285249
|
entity |
| Predicate | fixation |
P102733
|
FINISHED |
| Object | screens |
—
|
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: screens | Statement: [Mike Teavee, fixation, screens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixation Context triple: [Mike Teavee, fixation, screens]
-
A.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
-
B.
typeOfFixing
Indicates the specific method or manner in which one entity is fastened, attached, or secured to another.
-
C.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
D.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
E.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.