Triple
T35647609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D'deridex-class warbird |
E1030051
|
entity |
| Predicate | hasCloaking |
P194922
|
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: [D'deridex-class warbird, hasCloaking, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloaking Context triple: [D'deridex-class warbird, hasCloaking, true]
-
A.
isCloakedWhenBurrowed
Indicates that an entity becomes hidden or invisible (cloaked) whenever it is in a burrowed state.
-
B.
hasCloister
Indicates that one entity possesses or includes a cloister as part of its structure or layout.
-
C.
hiddenByMeansOf
Indicates that one entity is concealed or obscured through the use or application of another entity as the means of hiding.
-
D.
hasStealthGameplay
Indicates that the subject involves or supports gameplay mechanics centered around stealth, such as avoiding detection or silently bypassing opponents.
-
E.
hasHiddenImage
Indicates that an entity contains or is associated with an image that is not immediately visible or is intentionally concealed from normal view.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:05 p.m.