Triple
T11176084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceansat-3 |
E264414
|
entity |
| Predicate | regionOfObservation |
P90127
|
FINISHED |
| Object | global oceans |
—
|
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: global oceans | Statement: [Oceansat-3, regionOfObservation, global oceans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfObservation Context triple: [Oceansat-3, regionOfObservation, global oceans]
-
A.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
B.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
C.
observesRegion
chosen
Indicates that an entity monitors, watches, or collects information about a specific geographic or spatial region.
-
D.
locationOfObservance
Indicates the place where an event, ceremony, or observance occurs or is carried out.
-
E.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8987e1081909b28a0bdb866beae |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.