Triple
T26346324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Terminator |
E662784
|
entity |
| Predicate | setup |
P21642
|
FINISHED |
| Object | chair placed in front of opponent |
—
|
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: chair placed in front of opponent | Statement: [Van Terminator, setup, chair placed in front of opponent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setup Context triple: [Van Terminator, setup, chair placed in front of opponent]
-
A.
setUp
chosen
Indicates establishing, arranging, or preparing something so that it is ready for use or for a particular purpose.
-
B.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
C.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
D.
canonicalSetup
Indicates that an entity is arranged or configured in its standard, officially accepted, or authoritative form.
-
E.
typicalSetup
Indicates that an entity is arranged, configured, or organized in its standard or commonly used setup relative to another entity or context.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:42 p.m.