Triple
T25097907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Rican public university system |
E628640
|
entity |
| Predicate | policyBody |
P73269
|
FINISHED |
| Object | Consejo Nacional de Rectores |
—
|
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: Consejo Nacional de Rectores | Statement: [Costa Rican public university system, policyBody, Consejo Nacional de Rectores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyBody Context triple: [Costa Rican public university system, policyBody, Consejo Nacional de Rectores]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
policyDetail
Indicates that there is specific descriptive or explanatory information associated with a particular policy.
-
C.
policyOutput
Indicates that a policy or decision-making process produces or yields a particular outcome, result, or output.
-
D.
typeOfPolicyBody
chosen
Indicates that one entity is the governing or issuing body responsible for a particular policy type.
-
E.
policyElement
Indicates that something is a component or constituent part of a broader policy.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464ba4e148190a8169ac91b2f85b6 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.