Triple
T35791522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Ordinary Man |
E1034703
|
entity |
| Predicate | hasMaidCharacter |
P4079
|
FINISHED |
| Object | Tanja |
E1115742
|
NE 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: Tanja | Statement: [An Ordinary Man, hasMaidCharacter, Tanja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaidCharacter Context triple: [An Ordinary Man, hasMaidCharacter, Tanja]
-
A.
hasNannyCharacter
Indicates that one entity serves as a nanny or caregiver character for another entity.
-
B.
hasServant
chosen
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
C.
hasMummy
Indicates that an entity possesses or is associated with a mummy (preserved dead body).
-
D.
hasDomineeringMotherCharacter
Indicates that an entity is associated with a mother figure who exerts controlling, overbearing, or excessively authoritative influence over them.
-
E.
hasMermaidCharacter
Indicates that an entity includes, features, or is associated with a character who is a mermaid.
- F. None of above.
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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a02fcbe03d0819082d3dd715ed41623 |
completed | May 12, 2026, 10:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a389162047881908710fcaf86a56a19 |
completed | June 22, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_6a02fc62138081908d2dbc5db7541d13 |
completed | May 12, 2026, 10:09 a.m. |
Created at: May 3, 2026, 4:06 p.m.