Triple
T37872465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Jade Serpent |
E944638
|
entity |
| Predicate | hasChallengeModeRewards |
P199610
|
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: [Temple of the Jade Serpent, hasChallengeModeRewards, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChallengeModeRewards Context triple: [Temple of the Jade Serpent, hasChallengeModeRewards, yes]
-
A.
hasChallengeMode
Indicates that an entity offers or is associated with a special, typically more difficult, challenge-oriented mode or setting.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
hasRewardStatus
Indicates that an entity possesses a particular reward-related condition, level, or eligibility status within a reward system.
-
D.
hasBattlePassIntegration
Indicates that an entity is functionally connected to or supports features of a battle pass system.
-
E.
hasAchievements
Indicates that an entity possesses or is associated with one or more notable accomplishments, awards, or completed goals.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
| PDg | Predicate description generation | batch_69ff4818bb288190b4a27576fad18e23 |
completed | May 9, 2026, 2:43 p.m. |
Created at: May 3, 2026, 4:19 p.m.