Triple
T31131183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 12.0 |
E793510
|
entity |
| Predicate | hasNormalizationDataFile |
P70988
|
FINISHED |
| Object | Normalization.txt version 12.0.0 |
—
|
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: Normalization.txt version 12.0.0 | Statement: [Unicode 12.0, hasNormalizationDataFile, Normalization.txt version 12.0.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNormalizationDataFile Context triple: [Unicode 12.0, hasNormalizationDataFile, Normalization.txt version 12.0.0]
-
A.
haveNormalization
Indicates that one entity serves as a normalization or standardized form of another entity.
-
B.
hasDataFile
chosen
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
-
C.
usesNormalization
Indicates that one entity applies or relies on a normalization process or technique in relation to another entity or data.
-
D.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
E.
isNormalizableFor
Indicates that one entity can be transformed or converted into a standard or canonical form suitable for a particular process or context with respect to another entity.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: April 29, 2026, 9:05 p.m.