Triple
T8400780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bussokusekika |
E198164
|
entity |
| Predicate | metricalStructure |
P46136
|
FINISHED |
| Object | 5-7-5-7-7-7 morae |
—
|
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: 5-7-5-7-7-7 morae | Statement: [bussokusekika, metricalStructure, 5-7-5-7-7-7 morae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricalStructure Context triple: [bussokusekika, metricalStructure, 5-7-5-7-7-7 morae]
-
A.
metricalFeature
chosen
Indicates a relationship where one entity specifies or characterizes a metrical property or pattern of another entity.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
-
D.
mayHaveStructure
Indicates that an entity is allowed or able to possess a particular internal organization, configuration, or structural form, though not necessarily required to do so.
-
E.
localSymmetry
Indicates that an entity exhibits symmetry within a localized region or subset of its structure, rather than across its entire extent.
- 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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb824da3148190bfa3a1abfdfa02de |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.