Triple
T17688255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uncle Charlie Oakley |
E440951
|
entity |
| Predicate | hidesIdentityAs |
P20150
|
FINISHED |
| Object | beloved family uncle |
—
|
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: beloved family uncle | Statement: [Uncle Charlie Oakley, hidesIdentityAs, beloved family uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hidesIdentityAs Context triple: [Uncle Charlie Oakley, hidesIdentityAs, beloved family uncle]
-
A.
identityConcealedBy
Indicates that one entity hides, masks, or obscures the true identity of another entity.
-
B.
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.
-
C.
unawareOfTrueIdentityOf
Indicates that one entity does not know or recognize the real or actual identity of another entity.
-
D.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
-
E.
hidesFrom
Indicates that one entity actively avoids being seen, detected, or encountered by another entity.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704944d8819089b153aa14839fc0 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:03 a.m.