Triple
T33113037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cirth |
E847378
|
entity |
| Predicate | hasUnicodeProposal |
P188807
|
FINISHED |
| Object | proposed encoding for Cirth |
—
|
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: proposed encoding for Cirth | Statement: [Cirth, hasUnicodeProposal, proposed encoding for Cirth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnicodeProposal Context triple: [Cirth, hasUnicodeProposal, proposed encoding for Cirth]
-
A.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
-
B.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
-
C.
hasUnicodeStatus
Indicates that a given entity has a particular Unicode-related classification or status (such as assigned, reserved, deprecated, or noncharacter) within the Unicode standard.
-
D.
supportsUnicode
Indicates that an entity is capable of correctly handling, storing, or displaying Unicode-encoded text.
-
E.
hasProposedLanguage
Indicates that an entity has put forward or suggested a particular language, typically as a candidate for use, adoption, or standardization.
- F. None of above. chosen
Provenance (4 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.