Triple
T33700545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sylvia |
E863443
|
entity |
| Predicate | disguisePurpose |
P105027
|
FINISHED |
| Object | to gain freedom of movement |
—
|
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: to gain freedom of movement | Statement: [Sylvia, disguisePurpose, to gain freedom of movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disguisePurpose Context triple: [Sylvia, disguisePurpose, to gain freedom of movement]
-
A.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
B.
reasonForDisguise
chosen
Indicates the motive or purpose behind an entity adopting a disguise.
-
C.
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.
-
D.
disguisedStatus
Indicates that an entity is currently presenting a false or altered identity, appearance, or status to conceal its true nature.
-
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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8ca3808190be2fd9e5fb4c2146 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.