Triple
T34504487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duployan |
E885844
|
entity |
| Predicate | includedInUnicodeVersion |
—
|
GENERATED |
| Object | Unicode 7.0 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 1, 2026, 2:01 a.m.