Triple
T22020701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drone Mimic |
E543836
|
entity |
| Predicate | appearanceWhenDisguised |
P20150
|
FINISHED |
| Object | resembles a functional drone |
—
|
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: resembles a functional drone | Statement: [Drone Mimic, appearanceWhenDisguised, resembles a functional drone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearanceWhenDisguised Context triple: [Drone Mimic, appearanceWhenDisguised, resembles a functional drone]
-
A.
disguisedAs
chosen
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
B.
usesMasksOrDisguises
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
-
C.
reasonForDisguise
Indicates the motive or purpose behind an entity adopting a disguise.
-
D.
occupationInDisguise
Indicates that an entity’s true occupation is being concealed or performed under a false or hidden identity.
-
E.
headquartersDisguise
Indicates that an entity’s headquarters is concealed, misrepresented, or disguised as something else.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c7b3308190ac056bef6f82722e |
completed | April 28, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:23 p.m.