Triple
T38644962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurker |
E938690
|
entity |
| Predicate | cannotAttackWhenUnburrowed |
P193641
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lurker, cannotAttackWhenUnburrowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotAttackWhenUnburrowed Context triple: [Lurker, cannotAttackWhenUnburrowed, true]
-
A.
isCloakedWhenBurrowed
Indicates that an entity becomes hidden or invisible (cloaked) whenever it is in a burrowed state.
-
B.
canBurrow
Indicates that an entity has the ability to dig and create or use a burrow in the ground.
-
C.
detectionRequiredToSeeWhenBurrowed
Indicates that a special detection ability or condition is required to perceive an entity while it is in a burrowed or hidden state.
-
D.
canCastWhileBurrowed
Indicates that an entity is able to use or activate certain abilities or spells even while it is in a burrowed or underground state.
-
E.
notBuriedHere
Indicates that the entity in question is explicitly not buried at the specified location.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:32 p.m.