Triple
T4606529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tausug |
E100449
|
entity |
| Predicate | languageNameInOwnLanguage |
P52154
|
FINISHED |
| Object | Sinug |
—
|
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: Sinug | Statement: [Tausug, languageNameInOwnLanguage, Sinug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageNameInOwnLanguage Context triple: [Tausug, languageNameInOwnLanguage, Sinug]
-
A.
languageName
Indicates the specific name assigned to a language in the relationship.
-
B.
languageOfWorkOrName
Indicates the language in which a work is created or a name is expressed.
-
C.
localLanguageName
chosen
Indicates the name of a language as it is written or referred to in its own local or native form.
-
D.
hasNameInLocalLanguage
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
E.
originalNameLanguage
Indicates that the specified language is the language in which an entity’s original or primary name was expressed.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599c50d08190ab226cd0691e29f9 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.