Triple
T16143200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Costa Ricans |
E391712
|
entity |
| Predicate | militaryStatusOfCountry |
P104865
|
FINISHED |
| Object | no standing army |
—
|
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: no standing army | Statement: [Costa Ricans, militaryStatusOfCountry, no standing army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryStatusOfCountry Context triple: [Costa Ricans, militaryStatusOfCountry, no standing army]
-
A.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
-
B.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
C.
hasArmedForces
chosen
Indicates that an entity possesses or maintains organized military forces under its control.
-
D.
countryOfMilitaryService
Indicates that an entity served or is serving in the armed forces of a specified country.
-
E.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d91925c81909839a4e2f189d23b |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.