Triple
T27773316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagbanwa vowel sign U |
E699114
|
entity |
| Predicate | nameInUnicode |
P11609
|
FINISHED |
| Object | TAGBANWA VOWEL SIGN U |
—
|
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: TAGBANWA VOWEL SIGN U | Statement: [Tagbanwa vowel sign U, nameInUnicode, TAGBANWA VOWEL SIGN U]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameInUnicode Context triple: [Tagbanwa vowel sign U, nameInUnicode, TAGBANWA VOWEL SIGN U]
-
A.
hasUnicodeName
chosen
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
-
B.
nameInLatinAlphabet
Indicates that an entity’s name is written or represented using the Latin alphabet.
-
C.
nameInMcCuneReischauer
Indicates that an entity’s name is represented using the McCune–Reischauer romanization system.
-
D.
characterSetName
Indicates the name assigned to a particular character set used for encoding or representing characters.
-
E.
nameFormInLatin
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63798a67c8190876c47dacf89af6e |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:03 p.m.