Triple
T31912461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Show Jones |
E814723
|
entity |
| Predicate | usedDuringCareerPeriod |
P144081
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [No Show Jones, usedDuringCareerPeriod, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDuringCareerPeriod Context triple: [No Show Jones, usedDuringCareerPeriod, mid-20th century]
-
A.
timeInCareer
chosen
Indicates the point or duration within an entity’s professional or occupational trajectory at which a related event, status, or condition occurs.
-
B.
spentEntireCareerWith
Indicates that an individual has worked exclusively for a single organization or team for the full duration of their professional career.
-
C.
appliesDuringCareerPhase
Indicates that something is relevant or in effect only during a specified phase of an entity’s career.
-
D.
basedOnWorkPeriod
Indicates that something is determined, calculated, or defined according to a specific period of work or employment.
-
E.
employedAtTime
Indicates that an employment relationship holds during a specified time or time interval.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1bb923881909dd346a3739c91c8 |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:01 a.m.