Triple
T22050338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 3.1 |
E544865
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Unicode 3.2 |
—
|
NE NERFINISHED |
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 3.2 | Statement: [Unicode 3.1, followedBy, Unicode 3.2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unicode 3.2 Context triple: [Unicode 3.1, followedBy, Unicode 3.2]
-
A.
Unicode 3.2
chosen
Unicode 3.2 is a version of the Unicode Standard that expanded character coverage and refined existing scripts, contributing to broader global text representation in computing.
-
B.
Unicode 3.0
Unicode 3.0 is a major version of the Unicode Standard that significantly expanded character coverage, particularly for additional writing systems and symbols used worldwide.
-
C.
Unicode 3.1
Unicode 3.1 is a version of the Unicode Standard that significantly expanded character coverage, particularly for East Asian scripts and historic writing systems.
-
D.
Unicode 2.0
Unicode 2.0 is a major early version of the Unicode Standard that significantly expanded the character repertoire and refined the encoding model for global text representation.
-
E.
Unicode 6.3
Unicode 6.3 is a version of the Unicode Standard that introduced additional characters and refinements to support global text processing prior to the release of Unicode 7.0.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128323fb08190b9592fd08a96cba0 |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:26 p.m.