Triple
T30708007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW5000 |
E781805
|
entity |
| Predicate | designedForStealthApplications |
P17548
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [PW5000, designedForStealthApplications, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForStealthApplications Context triple: [PW5000, designedForStealthApplications, yes]
-
A.
isStealthUnit
Indicates that an entity functions as a unit specialized in remaining hidden or undetected from opponents.
-
B.
designedToAvoid
chosen
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
C.
concealability
Indicates the degree to which something can be hidden or kept from being noticed or discovered.
-
D.
hasStealthGameplay
Indicates that the subject involves or supports gameplay mechanics centered around stealth, such as avoiding detection or silently bypassing opponents.
-
E.
discreetUse
Indicates that something is used in a careful, unobtrusive, or low-profile manner so as not to attract attention.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 29, 2026, 8:35 p.m.