Triple
T29709230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munda Point |
E751728
|
entity |
| Predicate | supportingNavalOperations |
P18692
|
FINISHED |
| Object | United States Navy |
E551
|
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: United States Navy | Statement: [Munda Point, supportingNavalOperations, United States Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportingNavalOperations Context triple: [Munda Point, supportingNavalOperations, United States Navy]
-
A.
navalOperations
Indicates involvement in planning, conducting, or supporting military activities carried out by naval forces at sea or from the sea.
-
B.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
C.
navalSupportFrom
chosen
Indicates the provision of naval assistance or backing from one entity to another, such as military, logistical, or operational support delivered via sea forces.
-
D.
navalCooperation
Indicates a collaborative relationship between entities involving joint naval activities, operations, or support.
-
E.
navalOperationsInfluencedBy
Indicates that the planning, execution, or outcome of naval operations is shaped, guided, or affected by another factor, event, or entity.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26e5dec1d0819090154bff36b5110c |
completed | June 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:29 p.m.