Triple
T29089403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rieko Kodama |
E734812
|
entity |
| Predicate | industryTenure |
P144081
|
FINISHED |
| Object | 1980s–2010s |
—
|
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: 1980s–2010s | Statement: [Rieko Kodama, industryTenure, 1980s–2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: industryTenure Context triple: [Rieko Kodama, industryTenure, 1980s–2010s]
-
A.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
B.
workYear
Indicates the specific year or span of years during which an entity (such as a person or organization) was engaged in work or employment.
-
C.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
D.
timeInCareer
chosen
Indicates the point or duration within an entity’s professional or occupational trajectory at which a related event, status, or condition occurs.
-
E.
experienceDuration
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 11:03 a.m.