Triple
T24488540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 下つ巻 |
E617579
|
entity |
| Predicate | focusComparedToOtherVolumes |
P133705
|
FINISHED |
| Object | 神話よりも歴史的叙述が中心 |
—
|
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: 神話よりも歴史的叙述が中心 | Statement: [下つ巻, focusComparedToOtherVolumes, 神話よりも歴史的叙述が中心]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusComparedToOtherVolumes Context triple: [下つ巻, focusComparedToOtherVolumes, 神話よりも歴史的叙述が中心]
-
A.
volume
Indicates the amount of three-dimensional space an entity occupies or contains.
-
B.
scaleComparison
Indicates a relationship where two or more entities are compared in terms of their size, magnitude, or scale relative to one another.
-
C.
differenceInFocus
chosen
Indicates that two related items vary specifically in their emphasis, attention, or focal point rather than in their core content or identity.
-
D.
focusFactor
Indicates that one entity serves as a measure, component, or determinant of the degree of focus or concentration associated with another entity.
-
E.
densityComparedTo
Indicates a comparison between the densities of two entities, specifying which is denser or how their densities relate.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:22 a.m.