Triple
T27995211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-300F Fort |
E706993
|
entity |
| Predicate | navalizedVersionOf |
P56193
|
FINISHED |
| Object | S-300P |
E234559
|
NE 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: S-300P | Statement: [S-300F Fort, navalizedVersionOf, S-300P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalizedVersionOf Context triple: [S-300F Fort, navalizedVersionOf, S-300P]
-
A.
navalAnalogue
chosen
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
B.
nonNavalEquivalent
Indicates that one entity serves as the non-naval (e.g., land or air) counterpart or equivalent of another entity that is naval.
-
C.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
D.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
E.
navy
Indicates that an entity serves as or is associated with a nation's naval military force.
- F. None of above.
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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15b894bd288190a6a4f6d20075dc15 |
completed | May 26, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 7:52 p.m.