Triple
T16947183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Spatial Data Infrastructure Working Group |
E411095
|
entity |
| Predicate | concernsDataType |
P33715
|
FINISHED |
| Object | bathymetric data |
—
|
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: bathymetric data | Statement: [Marine Spatial Data Infrastructure Working Group, concernsDataType, bathymetric data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsDataType Context triple: [Marine Spatial Data Infrastructure Working Group, concernsDataType, bathymetric data]
-
A.
dataTypes
chosen
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
B.
analyzesDataType
Indicates that one entity examines, interprets, or evaluates a particular type or category of data.
-
C.
containsDataAbout
Indicates that one entity holds or includes information or records pertaining to another entity.
-
D.
concernsDate
Indicates that something is related or refers specifically to a particular date or point in time.
-
E.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb374588190b30230594aa418c6 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.