Triple
T29680194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Armed Forces |
E750928
|
entity |
| Predicate | reasonForNoNavy |
P184859
|
FINISHED |
| Object | landlocked country |
—
|
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: landlocked country | Statement: [Austrian Armed Forces, reasonForNoNavy, landlocked country]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForNoNavy Context triple: [Austrian Armed Forces, reasonForNoNavy, landlocked country]
-
A.
roleBeforeNavalService
Indicates that one role or position held by an individual occurred prior to that individual's naval service.
-
B.
hasNotableNavalRank
Indicates that an entity holds or has held a distinguished or significant rank within a naval organization.
-
C.
reasonForEnlistment
Indicates the motivation, cause, or circumstances that led an individual to join a military or similar organized service.
-
D.
usedInNavy
Indicates that something is or was employed, operated, or otherwise utilized by a navy or naval forces.
-
E.
nonNavalEquivalent
Indicates that one entity serves as the non-naval (e.g., land or air) counterpart or equivalent of another entity that is naval.
- F. None of above. chosen
Provenance (4 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 28, 2026, 7:10 p.m.