Triple
T29654907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Templar |
E750238
|
entity |
| Predicate | detectionRequirement |
P19703
|
FINISHED |
| Object | detector units |
—
|
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: detector units | Statement: [Dark Templar, detectionRequirement, detector units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectionRequirement Context triple: [Dark Templar, detectionRequirement, detector units]
-
A.
requiresDetectionOf
chosen
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
B.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
-
C.
inspectionRequired
Indicates that an entity must undergo an inspection before it can proceed, be used, or be approved.
-
D.
dialogRequirement
Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
-
E.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:54 p.m.