Triple
T15461230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Atlantic region |
E371902
|
entity |
| Predicate | isKeyProcessIn |
P118316
|
FINISHED |
| Object | Atlantic Ocean opening |
—
|
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: Atlantic Ocean opening | Statement: [Mid-Atlantic region, isKeyProcessIn, Atlantic Ocean opening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyProcessIn Context triple: [Mid-Atlantic region, isKeyProcessIn, Atlantic Ocean opening]
-
A.
keyProcess
Indicates that an entity plays a central, critical role in enabling or driving a particular process or workflow.
-
B.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
C.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
-
D.
keyProcessing
Indicates the handling or transformation of a key (such as generating, validating, encrypting, or otherwise operating on it) within a process or system.
-
E.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:32 a.m.