Triple
T28933160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibraltar sill |
E733841
|
entity |
| Predicate | isKeyControlOn |
P6727
|
FINISHED |
| Object | Mediterranean–Atlantic water mass exchange |
—
|
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: Mediterranean–Atlantic water mass exchange | Statement: [Gibraltar sill, isKeyControlOn, Mediterranean–Atlantic water mass exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyControlOn Context triple: [Gibraltar sill, isKeyControlOn, Mediterranean–Atlantic water mass exchange]
-
A.
isKeyModeIn
Indicates that one musical key functions as the mode or tonal framework within another key or harmonic context.
-
B.
isKeyStopOn
Indicates that a particular stop functions as a primary or significant stop along a specified route or service.
-
C.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
D.
keyState
chosen
Indicates the current status or condition of a key (such as pressed, released, locked, or unlocked) in relation to an associated object or system.
-
E.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 8:29 a.m.