Triple
T37662139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | spawnRarity |
P7075
|
FINISHED |
| Object | rare |
—
|
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: rare | Statement: [Chicken Jockey, spawnRarity, rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spawnRarity Context triple: [Chicken Jockey, spawnRarity, rare]
-
A.
rarity
chosen
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
rarityPattern
Indicates a relationship where an entity follows a specific distribution or pattern of rarity across a set of items, instances, or conditions.
-
C.
craftingRarity
Indicates the rarity level associated with crafting an item or outcome within a system.
-
D.
inUniverseRarity
Indicates how rare or uncommon something is within the context of a specific fictional or defined universe.
-
E.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.