Triple
T1639418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Navy |
E35432
|
entity |
| Predicate | armedForceBranchType |
P253
|
FINISHED |
| Object | maritime |
—
|
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: maritime | Statement: [Swiss Navy, armedForceBranchType, maritime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armedForceBranchType Context triple: [Swiss Navy, armedForceBranchType, maritime]
-
A.
hasMilitaryBranch
chosen
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
B.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
C.
militaryBranchEligibility
Indicates that an entity meets the required conditions to serve in a specified branch of the military.
-
D.
militaryBranchEmphasis
Indicates a relationship where a military branch is given particular focus, priority, or specialization within a broader military or organizational context.
-
E.
hasMilitaryDivision
Indicates that an entity possesses, includes, or is organizationally associated with a specific military division.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.