Triple
T18564454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutton SignWriting block |
E453726
|
entity |
| Predicate | blockRangeNotation |
P36590
|
FINISHED |
| Object | 1D800–1DAAF |
—
|
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: 1D800–1DAAF | Statement: [Sutton SignWriting block, blockRangeNotation, 1D800–1DAAF]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockRangeNotation Context triple: [Sutton SignWriting block, blockRangeNotation, 1D800–1DAAF]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
includesNumberingRange
chosen
Indicates that one entity contains or covers a specified contiguous range of numbers associated with another entity.
-
C.
rangeSection
Indicates a specific contiguous subset or span within a larger ordered range.
-
D.
rangeExpansion
Indicates an increase in the spatial or contextual extent over which something applies, operates, or is distributed.
-
E.
rangeIncludes
Indicates that the values or results associated with a property are expected to be of the specified type or types.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.