Triple
T11573343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinaray-a |
E274442
|
entity |
| Predicate | hasHonorificForms |
P9810
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Kinaray-a, hasHonorificForms, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHonorificForms Context triple: [Kinaray-a, hasHonorificForms, limited]
-
A.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
B.
hasHonorificSystem
chosen
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
-
C.
hasHonorificFrom
Indicates that one entity uses or receives a particular honorific title or form of address originating from another entity or source.
-
D.
hasHonorificNameIn
Indicates that an entity is referred to by a specific honorific or respectful name within a particular language, culture, or contextual setting.
-
E.
isHonorific
Indicates that one entity functions as an honorific title or respectful form of address applied to another entity.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89048120c81908258f984711f7dd4 |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.