Triple
T26828482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Worthing |
E675432
|
entity |
| Predicate | hasDoubleLifeLocation |
P165864
|
FINISHED |
| Object | country (as Jack) |
—
|
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: country (as Jack) | Statement: [Jack Worthing, hasDoubleLifeLocation, country (as Jack)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoubleLifeLocation Context triple: [Jack Worthing, hasDoubleLifeLocation, country (as Jack)]
-
A.
doubleLife
Indicates that an entity maintains two distinct, separate identities or lifestyles that are kept hidden from one another.
-
B.
hasDoppelganger
Indicates that an entity has a counterpart or double that closely resembles it, often in appearance, behavior, or role.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
hasHomeDualsAt
Indicates that an entity has corresponding dual (home/away or counterpart) versions located at a specified place or context.
-
E.
hasCursedLocation
Indicates a relationship where a location is affected by or associated with a curse.
- F. None of above. chosen
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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 27, 2026, 5 a.m.