Triple
T6757483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katakana |
E154499
|
entity |
| Predicate | hasNumberOfBasicCharacters |
P73319
|
FINISHED |
| Object | 46 |
—
|
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 | Statement: [Katakana, hasNumberOfBasicCharacters, 46]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfBasicCharacters Context triple: [Katakana, hasNumberOfBasicCharacters, 46]
-
A.
hasBasicLetters
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
B.
hasBlockUnicode
Indicates that one entity possesses or is associated with a specific Unicode block related to another entity.
-
C.
hasTextualCharacter
Indicates that something possesses or exhibits the qualities of written or printed text, such as letters, symbols, or characters.
-
D.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
-
E.
hasAdditionalUnicodeBlock
Indicates that an entity is associated with one or more supplementary Unicode character blocks beyond its primary assigned block.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d3264b7481908816a4d19543fb7b |
completed | March 27, 2026, 6:57 p.m. |
Created at: March 27, 2026, 2:11 p.m.