Triple
T24729716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mk 41 VLS |
E618249
|
entity |
| Predicate | locationOnShip |
P71679
|
FINISHED |
| Object | foredeck |
—
|
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: foredeck | Statement: [Mk 41 VLS, locationOnShip, foredeck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOnShip Context triple: [Mk 41 VLS, locationOnShip, foredeck]
-
A.
onboardLocation
chosen
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
-
B.
shipyardLocatedOn
Indicates that a shipyard is situated on or within the geographic area of a specified landmass, coastline, or body of water.
-
C.
locationOnKit
Indicates that an entity is located on or attached to a specific kit or equipment set.
-
D.
cargoHoldLocation
Indicates the specific place or compartment within a vehicle, vessel, or structure where cargo is stored or held.
-
E.
placeOfArrival
Indicates the location at which an entity or person arrives at the end of a journey, movement, or transfer.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:02 a.m.