Triple
T2169299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCISAT-1 |
E46984
|
entity |
| Predicate | studiesRegion |
P37341
|
FINISHED |
| Object | stratosphere |
—
|
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: stratosphere | Statement: [SCISAT-1, studiesRegion, stratosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesRegion Context triple: [SCISAT-1, studiesRegion, stratosphere]
-
A.
studiesForwardRegion
Indicates that an entity conducts study, analysis, or observation directed toward a forward or front-facing region relative to a reference point or object.
-
B.
searchesRegion
Indicates that an entity performs a search operation within, or targeting, a specified geographic or administrative region.
-
C.
populationRegion
Indicates that a specified population is located within or associated with a particular geographic region.
-
D.
demographicRegion
Indicates that an entity is associated with, belongs to, or is characterized by a particular geographic or administrative region for demographic purposes.
-
E.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
- F. None of above. chosen
Provenance (4 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abc153b22481908115e5f582c93f12 |
completed | March 7, 2026, 6:10 a.m. |
Created at: March 4, 2026, 7:45 p.m.