Triple
T3020551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tale of Genji |
E82442
|
entity |
| Predicate | laterPartFocus |
P35814
|
FINISHED |
| Object | lives of Kaoru and Niou |
—
|
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: lives of Kaoru and Niou | Statement: [The Tale of Genji, laterPartFocus, lives of Kaoru and Niou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPartFocus Context triple: [The Tale of Genji, laterPartFocus, lives of Kaoru and Niou]
-
A.
secondPartFocus
chosen
Indicates that the communicative or informational focus is placed on the second part or element in a two-part structure or relation.
-
B.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
formerFocus
Indicates that an entity previously served as the primary focus or main subject of attention, but no longer holds that status.
-
D.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
E.
focusAfterTransition
Indicates that focus is moved to a specific element or area after a transition or state change has completed.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a940c048190bc46e2c8001db8c0 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.