Triple
T38644969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurker |
E938690
|
entity |
| Predicate | requiresPlayerRace |
P98927
|
FINISHED |
| Object | Zerg |
—
|
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: Zerg | Statement: [Lurker, requiresPlayerRace, Zerg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPlayerRace Context triple: [Lurker, requiresPlayerRace, Zerg]
-
A.
raceInGame
Indicates that an entity participates as a race or faction within a particular game.
-
B.
playableRace
chosen
Indicates that an entity is a race or species that players are allowed to choose and control in a game or interactive system.
-
C.
alliedRaceUnlockRequirement
Indicates the conditions or prerequisites that must be met in order to unlock an allied race.
-
D.
usedByCharacterRace
Indicates that something (such as an item, ability, or feature) is utilized or employed by a particular character race.
-
E.
hasFeatureRace
Indicates that an entity includes, offers, or is associated with a specific race-related feature or race event.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a011d76f3f88190be3d7c9eb0552f34 |
completed | May 11, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_6a011cce684881909dd15776bb77a6e0 |
completed | May 11, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:32 p.m.