Triple
T23286489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mehetia |
E589000
|
entity |
| Predicate | hasSubmarineFlank |
P151708
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mehetia, hasSubmarineFlank, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmarineFlank Context triple: [Mehetia, hasSubmarineFlank, true]
-
A.
hasSubmarineExtension
Indicates that something possesses an additional part, feature, or capability specifically related to a submarine.
-
B.
hasFirstConfirmedSubmarineArrivalVessel
Indicates that a vessel is the first one confirmed to have arrived at a location by submarine.
-
C.
engagedSubmarines
Indicates that one entity took hostile or combat action against submarines belonging to another entity.
-
D.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
E.
submarine
Indicates that one entity is a submarine in relation to another entity or context.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19647178c8190bbca5da38472ce05 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 5 p.m.