Triple
T10467814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsman umbrella |
E246843
|
entity |
| Predicate | concealmentType |
P94192
|
FINISHED |
| Object | everyday object disguise |
—
|
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: everyday object disguise | Statement: [Kingsman umbrella, concealmentType, everyday object disguise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concealmentType Context triple: [Kingsman umbrella, concealmentType, everyday object disguise]
-
A.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
hidingPlace
Indicates a location or object that serves as a concealed or secret place where something or someone is hidden.
-
C.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
D.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
-
E.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092e3230819098ab444f73c9bd40 |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:20 p.m.