Triple
T18599877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cypriot Syllabary block |
E454590
|
entity |
| Predicate | definedInVersion |
P11235
|
FINISHED |
| Object | Unicode 4.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: Unicode 4.0 | Statement: [Cypriot Syllabary block, definedInVersion, Unicode 4.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedInVersion Context triple: [Cypriot Syllabary block, definedInVersion, Unicode 4.0]
-
A.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
-
B.
definesVersionOf
Indicates that one entity specifies or establishes the version or variant identity of another entity.
-
C.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
D.
usedInVersionRange
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
E.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5475018548190a2f497081af7ce55 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:45 a.m.