Triple
T784806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Rica |
E16577
|
entity |
| Predicate | abolishedMilitary |
P9916
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Costa Rica, abolishedMilitary, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedMilitary Context triple: [Costa Rica, abolishedMilitary, 1948]
-
A.
abolishedConcept
Indicates that one entity has formally ended, eliminated, or done away with the other entity as a concept, practice, or institution.
-
B.
militaryUseEnd
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
C.
demobilization
chosen
Indicates the process by which armed forces or combatants are formally released from military service and military structures are reduced or disbanded.
-
D.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
E.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
- 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_69a4936ad1fc81908f190208059ccf78 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a769dc6481908f12e872f997acf3 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.