Triple
T228217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin-1 Supplement |
E4357
|
entity |
| Predicate | rangeEnd |
P9332
|
FINISHED |
| Object | U+00FF |
—
|
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: U+00FF | Statement: [Latin-1 Supplement, rangeEnd, U+00FF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeEnd Context triple: [Latin-1 Supplement, rangeEnd, U+00FF]
-
A.
range
Indicates that a value, property, or effect extends between specified limits or over a specified interval or scope.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
rangeCapability
Indicates the maximum distance or extent over which an entity can effectively operate, function, or exert its effect.
-
D.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
E.
endsWith
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other entity.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25d0ec71081908478c800be4f7bb0 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.