Triple
T18334357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Tasker |
E439229
|
entity |
| Predicate | coverIdentityDescription |
P114813
|
FINISHED |
| Object | ordinary family man |
—
|
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: ordinary family man | Statement: [Harry Tasker, coverIdentityDescription, ordinary family man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverIdentityDescription Context triple: [Harry Tasker, coverIdentityDescription, ordinary family man]
-
A.
characterCoverIdentity
chosen
Indicates that one character uses another identity as a cover or disguise, typically concealing their true identity.
-
B.
coverIdentityFather
Indicates that one entity conceals, disguises, or assumes the identity of another entity who is the father.
-
C.
appearsInIdentity
Indicates that an entity is featured, referenced, or plays a role within a particular identity or identity-related context.
-
D.
coverIdentities
Indicates that one entity conceals, masks, or protects the true identities of one or more other entities.
-
E.
coverRole
Indicates that one entity temporarily assumes or fills the role, duties, or position normally held 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecc91148190aa820fcd466009ce |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.