Triple
T33465042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wemmick |
E857021
|
entity |
| Predicate | hasDualLife |
P138711
|
FINISHED |
| Object | Professional life at office |
—
|
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: Professional life at office | Statement: [Wemmick, hasDualLife, Professional life at office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDualLife Context triple: [Wemmick, hasDualLife, Professional life at office]
-
A.
doubleLife
chosen
Indicates that an entity maintains two distinct, separate identities or lifestyles that are kept hidden from one another.
-
B.
hasDoubleLifeLocation
Indicates that an entity maintains a second, secret or alternate place where it lives or operates in parallel to its primary location.
-
C.
hasHomeDualsAt
Indicates that an entity has corresponding dual (home/away or counterpart) versions located at a specified place or context.
-
D.
hasDualSpace
Indicates that one mathematical space is the dual space consisting of all linear functionals defined on another space.
-
E.
hasDualCareer
Indicates that an entity simultaneously maintains two distinct professional roles or career paths.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4f996948190a20e96059d5188cc |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.