Triple
T38593237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Visor |
E932501
|
entity |
| Predicate | targetingCondition |
P199357
|
FINISHED |
| Object | Requires line of sight to enemies |
—
|
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: Requires line of sight to enemies | Statement: [Tactical Visor, targetingCondition, Requires line of sight to enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetingCondition Context triple: [Tactical Visor, targetingCondition, Requires line of sight to enemies]
-
A.
targetedCondition
Indicates that an action, intervention, or entity is specifically directed toward affecting, treating, or addressing a particular condition.
-
B.
targetingRule
chosen
Indicates a rule that defines which entities are selected or targeted based on specified conditions or criteria.
-
C.
scopeCondition
Indicates the specific conditions or constraints under which something is valid, applicable, or in effect within a given scope.
-
D.
featuresCondition
Indicates that an entity includes, exhibits, or is characterized by a particular condition.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4:32 p.m.