Triple
T19276834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 5.2 |
E482078
|
entity |
| Predicate | extendsCoverage |
P1673
|
FINISHED |
| Object | historic scripts |
—
|
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: historic scripts | Statement: [Unicode 5.2, extendsCoverage, historic scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsCoverage Context triple: [Unicode 5.2, extendsCoverage, historic scripts]
-
A.
impliesCoverage
Indicates that one entity’s scope, protection, or applicability extends to or includes another entity.
-
B.
expansionCoverage
Indicates the extent to which a given expansion (such as a geographic, functional, or service-area enlargement) is applied or covered within a specified scope or domain.
-
C.
extendsTo
chosen
Indicates that one entity reaches, stretches, or continues its scope, influence, or coverage up to or into another entity.
-
D.
extendedFrom
Indicates that one entity is derived by adding to or building upon the scope, content, or structure of another entity.
-
E.
extendedBy
Indicates that one entity builds upon, enlarges, or adds to the scope, functionality, or duration of 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbbd5f34819086535f28fd880411 |
completed | April 20, 2026, 10:11 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:29 p.m.