Triple
T1380399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico class |
E29323
|
entity |
| Predicate | typicalOperations |
P689
|
FINISHED |
| Object | shore bombardment |
—
|
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: shore bombardment | Statement: [New Mexico class, typicalOperations, shore bombardment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOperations Context triple: [New Mexico class, typicalOperations, shore bombardment]
-
A.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
B.
notableOperationType
Indicates that an entity is associated with a specific type or category of operation that is considered notable or significant.
-
C.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
operationType
chosen
Indicates the specific kind of operation or action being performed or recorded in the relationship between entities.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c319f46481909ba8a69a19b865e5 |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befe343c81909f758440a531b5be |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.