Triple
T37458856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinkertown Technician |
E930866
|
entity |
| Predicate | battlecryCondition |
P29885
|
FINISHED |
| Object | If you have a Mech |
—
|
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: If you have a Mech | Statement: [Tinkertown Technician, battlecryCondition, If you have a Mech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battlecryCondition Context triple: [Tinkertown Technician, battlecryCondition, If you have a Mech]
-
A.
conditionForBattle
Indicates that one situation, state, or requirement must be satisfied in order for a battle or combat event to occur.
-
B.
conditionDuringBattle
Indicates that a specified condition or state holds true for an entity while a particular battle or combat event is taking place.
-
C.
conditionOfVictory
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
D.
conditionToSummon
Indicates that a specific condition or set of conditions must be met in order for an entity to be summoned.
-
E.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.