Triple
T4117303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casa de Osambela |
E90322
|
entity |
| Predicate | languageOfSurroundingCommunity |
P11430
|
FINISHED |
| Object | Spanish |
—
|
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: Spanish | Statement: [Casa de Osambela, languageOfSurroundingCommunity, Spanish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfSurroundingCommunity Context triple: [Casa de Osambela, languageOfSurroundingCommunity, Spanish]
-
A.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
B.
majorityLanguageOf
chosen
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
C.
languageFamilyDominant
Indicates that one language family holds a primary or prevailing status over others within a given context (such as a region, population, or system).
-
D.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
E.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.