Triple
T38616011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iyayu language |
E934617
|
entity |
| Predicate | hasLimitedOfficialRecognition |
P43114
|
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: [Iyayu language, hasLimitedOfficialRecognition, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLimitedOfficialRecognition Context triple: [Iyayu language, hasLimitedOfficialRecognition, true]
-
A.
hasOfficialRecognition
Indicates that an entity has been formally acknowledged or approved by an authorized body or institution.
-
B.
hasLimitedRecognition
chosen
Indicates that the subject is acknowledged or accepted only to a small extent, in restricted contexts, or by a limited audience.
-
C.
meetsInCountryWithLimitedRecognition
Indicates that two or more entities meet in a country whose international recognition as a sovereign state is limited or disputed.
-
D.
hasMunicipalRecognition
Indicates that an entity is officially acknowledged or recognized by a municipal (city or local) government authority.
-
E.
historicallyNotFullyRecognizedBy
Indicates that one entity has not been fully acknowledged, accepted, or given proper status by another entity throughout history.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 3, 2026, 4:32 p.m.