Triple
T27773302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagbanwa vowel sign U |
E699114
|
entity |
| Predicate | canonicalCombiningClass |
P164347
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Tagbanwa vowel sign U, canonicalCombiningClass, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canonicalCombiningClass Context triple: [Tagbanwa vowel sign U, canonicalCombiningClass, 0]
-
A.
hasCanonicalCombiningClassMarks
Indicates that an entity has associated marks whose Unicode canonical combining class is explicitly defined or recognized.
-
B.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
-
C.
UnicodePlane
Indicates that a Unicode code point belongs to a specific Unicode plane (a contiguous range of code points grouped by plane number).
-
D.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
E.
NFKC
Indicates that a string has been normalized using Unicode Normalization Form KC, meaning compatibility-equivalent characters are transformed into a canonical, standardized representation.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 5:03 p.m.