Triple
T37662147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | canSpawnWithEquipment |
P189520
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chicken Jockey, canSpawnWithEquipment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSpawnWithEquipment Context triple: [Chicken Jockey, canSpawnWithEquipment, true]
-
A.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
B.
canSpawnWithProfessionOutfit
Indicates that an entity is able to appear or be generated wearing an outfit associated with a specific profession.
-
C.
canSpawnCondition
Indicates that the ability to spawn or be generated is dependent on a specific condition being met.
-
D.
canUseHero
Indicates that an entity is permitted or able to use a specified hero character.
-
E.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:18 p.m.