Triple
T6684612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacto de San José de Costa Rica |
E152068
|
entity |
| Predicate | estructura |
P17710
|
FINISHED |
| Object | Preámbulo |
—
|
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: Preámbulo | Statement: [Pacto de San José de Costa Rica, estructura, Preámbulo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estructura Context triple: [Pacto de San José de Costa Rica, estructura, Preámbulo]
-
A.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
B.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
D.
segmentStructure
chosen
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
E.
proposedStructure
Indicates that one entity has suggested or put forward another entity as a potential structure or structural arrangement.
- 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_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. |
Created at: March 27, 2026, 2:04 p.m.