Triple
T32429153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Montgomery (LCS-8) |
E828668
|
entity |
| Predicate | missionModules |
P176368
|
FINISHED |
| Object | surface warfare module |
—
|
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: surface warfare module | Statement: [USS Montgomery (LCS-8), missionModules, surface warfare module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionModules Context triple: [USS Montgomery (LCS-8), missionModules, surface warfare module]
-
A.
missionCommandModule
Indicates that one entity serves as the command module component of a mission involving the other entity.
-
B.
crewModule
Indicates that an object functions as or contains a crew module, i.e., a section designed to house and support crew members.
-
C.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
-
D.
missionPatchFeature
Indicates that one entity features or includes another as a design element on a mission patch.
-
E.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 12:54 a.m.