Triple
T38644938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lurker |
E938690
|
entity |
| Predicate | techTreeRequirement |
P165835
|
FINISHED |
| Object | Hydralisk Den |
—
|
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: Hydralisk Den | Statement: [Lurker, techTreeRequirement, Hydralisk Den]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: techTreeRequirement Context triple: [Lurker, techTreeRequirement, Hydralisk Den]
-
A.
componentRequirement
chosen
Indicates that one component depends on or necessitates the presence or use of another component to function or be considered complete.
-
B.
unitRequirement
Indicates that one entity specifies a required quantity or unit that another entity must meet or conform to.
-
C.
projectRequirement
Indicates that one entity specifies a necessary condition, resource, or criterion that must be satisfied for a project associated with another entity.
-
D.
planningRequirement
Indicates that one entity imposes or specifies a planning-related obligation, condition, or prerequisite that must be satisfied by another entity or activity.
-
E.
technicalDemand
Indicates that one entity requires or imposes a certain level of technical skill, complexity, or resources on another entity.
- 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_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.