Triple
T34759089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pugliese torpedo defense system |
E1002014
|
entity |
| Predicate | locationInShip |
P71679
|
FINISHED |
| Object | between outer hull and internal bulkhead |
—
|
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: between outer hull and internal bulkhead | Statement: [Pugliese torpedo defense system, locationInShip, between outer hull and internal bulkhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInShip Context triple: [Pugliese torpedo defense system, locationInShip, between outer hull and internal bulkhead]
-
A.
locationDuringCruise
Indicates that an entity’s location is specified for the duration of a cruise or while a cruise is taking place.
-
B.
locationOnSpacecraft
Indicates that one entity occupies or is situated at a specific place or position on a spacecraft.
-
C.
aboardShip
Indicates that one entity is physically on or inside a ship, typically as a passenger, crew member, or cargo.
-
D.
locationOnAircraft
Indicates that one entity is physically situated on or within an aircraft.
-
E.
onboardLocation
chosen
Indicates that one entity is located on or within a vehicle, vessel, or other conveyance associated with another entity.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.