Triple
T12702697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegean back-arc extension |
E303500
|
entity |
| Predicate | observedThrough |
P20345
|
FINISHED |
| Object | seismic reflection 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: seismic reflection data | Statement: [Aegean back-arc extension, observedThrough, seismic reflection data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedThrough Context triple: [Aegean back-arc extension, observedThrough, seismic reflection data]
-
A.
observedVia
chosen
Indicates that something is perceived, detected, or measured through a particular medium, instrument, method, or channel.
-
B.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
C.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
D.
observedAs
Indicates that one entity is perceived, recorded, or identified in the role, state, or form of another entity.
-
E.
observedWith
Indicates that two or more entities are seen, detected, or recorded together in the same context, event, or observation.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.