Triple
T33404672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean Jacket |
E855405
|
entity |
| Predicate | camouflagedAs |
P20150
|
FINISHED |
| Object | classic flying saucer |
—
|
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: classic flying saucer | Statement: [Jean Jacket, camouflagedAs, classic flying saucer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: camouflagedAs Context triple: [Jean Jacket, camouflagedAs, classic flying saucer]
-
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.
canCamouflage
Indicates that an entity has the ability to blend into its surroundings or alter its appearance to avoid detection.
-
C.
camouflageStyle
Indicates the type or pattern of camouflage used to visually conceal or disguise an entity in its environment.
-
D.
camouflageTerm
Indicates that one entity serves as a camouflage-related term or label used to describe the concealment or disguising of another entity.
-
E.
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.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:36 a.m.