Triple
T15783116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARPAC |
E382668
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | MARPAC |
E382668
|
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: MARPAC | Statement: [MARPAC, hasAbbreviation, MARPAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MARPAC Context triple: [MARPAC, hasAbbreviation, MARPAC]
-
A.
MARPAC
chosen
MARPAC is the commonly used abbreviation for Maritime Forces Pacific, the Royal Canadian Navy formation responsible for naval operations in the Pacific region.
-
B.
MARFORPAC
MARFORPAC is the United States Marine Corps’ major operational command responsible for Marine forces in the Indo-Pacific region.
-
C.
SOPAC
SOPAC is a regional performing arts center in South Orange, New Jersey, hosting a variety of live music, theater, comedy, and community events.
-
D.
SOPAC
SOPAC was the World War II Allied military command responsible for coordinating operations across the South Pacific Area.
-
E.
Harbor Master Unit
The Harbor Master Unit is a specialized division of the Detroit Police Department responsible for law enforcement, safety, and emergency response on the city’s waterways and harbor areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05400716881909bc43212c8ea54d5 |
completed | April 16, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff90a2476c8190a153fb47cb4e7708 |
completed | May 9, 2026, 7:53 p.m. |
Created at: April 10, 2026, 4:48 a.m.