Triple
T11067763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEOSCOPE global seismological network |
E261668
|
entity |
| Predicate | dataTypeRecorded |
P4241
|
FINISHED |
| Object | broadband seismic 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: broadband seismic data | Statement: [GEOSCOPE global seismological network, dataTypeRecorded, broadband seismic data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeRecorded Context triple: [GEOSCOPE global seismological network, dataTypeRecorded, broadband seismic data]
-
A.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
B.
recordingType
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
dataTypeSynced
Indicates that the data type of one entity has been successfully synchronized to match the data type of another entity or an external source.
-
E.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79920428c81908db824ab54e08e8d |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.