Triple
T37460666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haunted Creeper |
E930907
|
entity |
| Predicate | tokenTribe |
P21054
|
FINISHED |
| Object | Beast |
—
|
NE NERFINISHED |
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: Beast | Statement: [Haunted Creeper, tokenTribe, Beast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tokenTribe Context triple: [Haunted Creeper, tokenTribe, Beast]
-
A.
nativeTokenOf
Indicates that a given token is the primary, built-in (native) currency or asset of a specified blockchain or platform.
-
B.
sharesTribeWith
chosen
Indicates that two entities belong to the same tribe or tribal group.
-
C.
inTribe
Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
-
D.
tribeSynergy
Indicates a cooperative or mutually enhancing relationship among members of the same tribe or group, where their combined presence or actions produce greater overall effectiveness than they would individually.
-
E.
usedByTribe
Indicates that something is utilized or employed by a particular tribe.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.