Triple
T28827384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrc |
E727945
|
entity |
| Predicate | appliesToUnicodeBlock |
P146896
|
FINISHED |
| Object | Syriac Unicode block |
—
|
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: Syriac Unicode block | Statement: [Syrc, appliesToUnicodeBlock, Syriac Unicode block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToUnicodeBlock Context triple: [Syrc, appliesToUnicodeBlock, Syriac Unicode block]
-
A.
hasBlockUnicode
Indicates that one entity possesses or is associated with a specific Unicode block related to another entity.
-
B.
hasAdditionalUnicodeBlock
Indicates that an entity is associated with one or more supplementary Unicode character blocks beyond its primary assigned block.
-
C.
hasDedicatedUnicodeBlock
chosen
Indicates that a given writing system, symbol set, or character group is assigned its own specific, contiguous range of code points in the Unicode standard.
-
D.
hasUnicodeBlockAlias
Indicates that one Unicode block is known or referenced by an alternative name (alias).
-
E.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 28, 2026, 6:36 a.m.