Triple
T6684581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacto de San José de Costa Rica |
E152068
|
entity |
| Predicate | idiomasOficiales |
P71740
|
FINISHED |
| Object | español |
—
|
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: español | Statement: [Pacto de San José de Costa Rica, idiomasOficiales, español]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idiomasOficiales Context triple: [Pacto de San José de Costa Rica, idiomasOficiales, español]
-
A.
shareOfficialLanguage
Indicates that two entities have at least one official language in common.
-
B.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
C.
previousOfficialLanguage
Indicates that one language formerly held official status in a country, region, or organization before being replaced or losing that status.
-
D.
languageOfOfficialLists
Indicates the language in which official lists, records, or registries are formally maintained or published.
-
E.
haveDistinctOfficialLanguages
Indicates that the two entities each have their own official language and these official languages are not the same.
- F. None of above. chosen
Provenance (4 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c0aa8c5c8190a302b261f11b70cb |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0b6d00819086205b8ce30dd045 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6c0a90a088190978061cb05dbe268 |
completed | March 27, 2026, 5:38 p.m. |
Created at: March 27, 2026, 2:04 p.m.