Triple
T27773307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagbanwa vowel sign U |
E699114
|
entity |
| Predicate | combining |
P70656
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Tagbanwa vowel sign U, combining, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combining Context triple: [Tagbanwa vowel sign U, combining, Yes]
-
A.
combinedIn
Indicates that two or more entities are merged, joined, or used together to form a single combined whole or context.
-
B.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
-
C.
laterCombination
Indicates that one entity is a combination or composite that occurs after, or is formed subsequent to, another entity or state.
-
D.
knownForCombining
Indicates a relationship where one entity is recognized or notable for bringing together or merging multiple elements, entities, or aspects into a unified whole.
-
E.
combiningClass
chosen
Indicates that one entity functions as a combining diacritic or mark that attaches to a base character, specifying how it combines in text rendering or encoding.
- 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_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 5:03 p.m.