Triple
T34504487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duployan |
E885844
|
entity |
| Predicate | includedInUnicodeVersion |
P23128
|
FINISHED |
| Object | Unicode 7.0 |
E254460
|
NE 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 7.0 | Statement: [Duployan, includedInUnicodeVersion, Unicode 7.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInUnicodeVersion Context triple: [Duployan, includedInUnicodeVersion, Unicode 7.0]
-
A.
UnicodeStandardVersionIntroduced
chosen
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
B.
encodedInUnicodeSince
Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
-
C.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
-
D.
hasUnicodeVariant
Indicates that one entity has an alternative representation or equivalent form in Unicode corresponding to the other entity.
-
E.
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.
- F. None of above.
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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3736160eb4819091d21826f898332b |
completed | June 21, 2026, 12:53 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.