Triple
T38644932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurker |
E938690
|
entity |
| Predicate | requiresBurrowToAttack |
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, requiresBurrowToAttack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBurrowToAttack Context triple: [Lurker, requiresBurrowToAttack, true]
-
A.
requiresForAggression
Indicates that one entity must possess, obtain, or satisfy another entity or condition as a prerequisite in order to carry out an aggressive action.
-
B.
cannotAttackWhenUnburrowed
chosen
Indicates that an entity is unable to perform attacks while it is in the unburrowed state.
-
C.
canBeAttackedBy
Indicates that an entity is a possible target of an attack initiated by another entity.
-
D.
mustRootToAttack
Indicates that an entity is required to become immobile or stationary (rooted) as a prerequisite in order to perform an attack.
-
E.
forceAttacked
Indicates that one entity carried out an attack against another entity using force or coercive power.
- 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_6a0119132e848190820a688d139fbf75 |
completed | May 10, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a01188dfdec8190b7f675264a281733 |
completed | May 10, 2026, 11:45 p.m. |
Created at: May 3, 2026, 4:32 p.m.