Triple
T32748358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keiko Miura |
E837421
|
entity |
| Predicate | employerActivity |
P53735
|
FINISHED |
| Object | study of Titans |
—
|
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: study of Titans | Statement: [Keiko Miura, employerActivity, study of Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerActivity Context triple: [Keiko Miura, employerActivity, study of Titans]
-
A.
employerIn
Indicates that one entity serves as the employer of another within a specified context, such as a location, organization, or time period.
-
B.
employerService
Indicates that one entity provides employment-related services or functions to another entity, typically in the role of an employer.
-
C.
commonEmployment
Indicates that two or more entities share the same employer or have worked for the same organization.
-
D.
employerFocus
chosen
Indicates that an employer directs particular attention, resources, or priority toward a specific subject, group, or area.
-
E.
businessActivities
Indicates the commercial operations, transactions, or services that an entity conducts as part of its business.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:12 a.m.