Triple
T38644961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurker |
E938690
|
entity |
| Predicate | hasUnburrowedState |
P195220
|
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, hasUnburrowedState, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnburrowedState Context triple: [Lurker, hasUnburrowedState, true]
-
A.
hasBurrowedState
Indicates that an entity is in a condition or status of having burrowed into or beneath a surface or substrate.
-
B.
hasGroundState
Indicates that an entity possesses a lowest-energy, most stable state in its energy configuration.
-
C.
isMobileWhenBurrowed
Indicates that an entity remains capable of movement while it is burrowed.
-
D.
detectionRequiredToSeeWhenBurrowed
Indicates that a special detection ability or condition is required to perceive an entity while it is in a burrowed or hidden state.
-
E.
hasStateBranch
Indicates that one entity functions as a branch, subdivision, or local office of a larger parent entity within a particular state or regional jurisdiction.
- 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_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69fdb04d37288190969a0f39d92efb49 |
completed | May 8, 2026, 9:43 a.m. |
Created at: May 3, 2026, 4:32 p.m.