Triple
T7735817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kana |
E175376
|
entity |
| Predicate | standardSetSize |
P78422
|
FINISHED |
| Object | 46 basic characters per syllabary |
—
|
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: 46 basic characters per syllabary | Statement: [Kana, standardSetSize, 46 basic characters per syllabary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardSetSize Context triple: [Kana, standardSetSize, 46 basic characters per syllabary]
-
A.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
B.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
C.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
D.
sampleSize
Indicates the number of units, observations, or instances included in a particular study, experiment, or dataset.
-
E.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
- 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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:06 p.m.