Triple
T32748365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keiko Miura |
E837421
|
entity |
| Predicate | hasSecretiveEmployer |
P162272
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Keiko Miura, hasSecretiveEmployer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecretiveEmployer Context triple: [Keiko Miura, hasSecretiveEmployer, true]
-
A.
employedIncognito
Indicates that one entity is working for or employed by another while deliberately concealing their true identity or role.
-
B.
secretlyIs
chosen
Indicates that one entity possesses a hidden or undisclosed identity, role, or attribute in relation to another entity.
-
C.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
D.
hasKeyEmployer
Indicates that an entity has a primary or main employer with which it holds a significant employment relationship.
-
E.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 1, 2026, 1:12 a.m.