Triple
T6766077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimotsumaki |
E154721
|
entity |
| Predicate | lessFocusOn |
P73140
|
FINISHED |
| Object | mythological narratives |
—
|
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: mythological narratives | Statement: [Shimotsumaki, lessFocusOn, mythological narratives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lessFocusOn Context triple: [Shimotsumaki, lessFocusOn, mythological narratives]
-
A.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
canonicalFocus
Indicates that one entity is the primary or most representative focus or point of attention in relation to another entity.
-
C.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
D.
mayProvideFocus
Indicates that one entity can potentially direct attention, emphasis, or concentration toward another entity or aspect.
-
E.
focusMechanism
Indicates the method or process by which attention or emphasis is directed toward a particular entity or aspect within a context.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d22ed30881909e1bfcfb8cf175a2 |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:12 p.m.