Triple
T24475639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Rican Olympic Committee |
E617223
|
entity |
| Predicate | representsCountryCode |
P92608
|
FINISHED |
| Object | CRC |
—
|
NE NERFINISHED |
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: CRC | Statement: [Costa Rican Olympic Committee, representsCountryCode, CRC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsCountryCode Context triple: [Costa Rican Olympic Committee, representsCountryCode, CRC]
-
A.
associatedCountryCode
Indicates that there is a relationship linking something to the country identified by the given country code.
-
B.
representsISO3166Code
Indicates that one entity is designated as the ISO 3166 country (or subdivision) code corresponding to the other entity.
-
C.
countryRepresenting
Indicates that one entity serves as the official representative or acting country on behalf of another entity in a given context.
-
D.
isCountryCode
chosen
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
E.
countryRepresented
Indicates that one entity serves as the official representative (such as an athlete, diplomat, or delegate) of a specific country in a given context or event.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29947084081908895573a4a4e4822 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.