Triple
T37554397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgement Legplates |
E933659
|
entity |
| Predicate | gameplayEra |
P190729
|
FINISHED |
| Object | vanilla raiding |
—
|
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: vanilla raiding | Statement: [Judgement Legplates, gameplayEra, vanilla raiding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayEra Context triple: [Judgement Legplates, gameplayEra, vanilla raiding]
-
A.
playedWithEra
Indicates that an entity performed or was active during a specified historical or stylistic era.
-
B.
hasApproximateEraOfPlayers
Indicates that two or more players are associated with roughly the same time period or era in which they were active.
-
C.
competitionEra
Indicates the historical or contextual period during which a particular competition or competitive event took place.
-
D.
screenTimeEra
Indicates the period or era during which a particular screen-based technology, medium, or usage pattern is prevalent or characteristic.
-
E.
tradeEra
Indicates the historical period or era during which a trade or commercial activity takes place or is characteristic.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.