Triple
T24129433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangyan languages |
E597901
|
entity |
| Predicate | haveTraditionalSyllabicScripts |
P9809
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mangyan languages, haveTraditionalSyllabicScripts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveTraditionalSyllabicScripts Context triple: [Mangyan languages, haveTraditionalSyllabicScripts, true]
-
A.
hasSyllabary
chosen
Indicates that one entity possesses or is associated with a specific syllabary writing system used to represent its language or notation.
-
B.
hasSyllabicStructure
Indicates that an entity possesses a specific arrangement or pattern of syllables, such as their number, order, or type.
-
C.
hasTraditionalDialect
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
-
D.
hasTraditionalCharacter
Indicates that an entity is associated with or represented by a traditional (non-simplified or historically established) written character form.
-
E.
hasOfficialWritingSystem
Indicates that an entity (typically a language) is associated with a formally recognized and standardized writing system used for official or standard purposes.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7644808190b4bbbf4db1539f48 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:23 p.m.