Triple
T4575212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrillic Supplement |
E123126
|
entity |
| Predicate | assignedInVersion |
P5706
|
FINISHED |
| Object | Unicode 3.2 |
—
|
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 3.2 | Statement: [Cyrillic Supplement, assignedInVersion, Unicode 3.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedInVersion Context triple: [Cyrillic Supplement, assignedInVersion, Unicode 3.2]
-
A.
assignedTo
Indicates that responsibility for a task, item, or role has been designated to a specific entity.
-
B.
assignedInStandard
chosen
Indicates that something is allocated or designated within a defined standard, specification, or normative framework.
-
C.
assignedUnder
Indicates that one entity has been given responsibility, duty, or authority to act within the scope, supervision, or framework defined by another entity.
-
D.
assignedToState
Indicates that something has been allocated or designated to a particular state or status.
-
E.
historicallyAssignedTo
Indicates that something was associated with or allocated to a particular entity during a past period, but may no longer be so in the present.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c9f0bc81908d87f01ab067818a |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.