Triple
T36960476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Cannon |
E914293
|
entity |
| Predicate | supportsModSwitching |
P192141
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Heavy Cannon, supportsModSwitching, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsModSwitching Context triple: [Heavy Cannon, supportsModSwitching, yes]
-
A.
hasModeSwitching
chosen
Indicates that an entity supports changing between different operational modes or states.
-
B.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
-
C.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
D.
supportsTransitions
Indicates that one entity enables, allows, or is compatible with changes from one state or condition to another.
-
E.
hasModeInterchange
Indicates a relationship where one transportation mode can be transferred or switched to another at a specific point or facility.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.