Triple
T22998938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Ecliptic Pole |
E572582
|
entity |
| Predicate | isObservationRegionFor |
P90127
|
FINISHED |
| Object | infrared sky surveys |
—
|
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: infrared sky surveys | Statement: [North Ecliptic Pole, isObservationRegionFor, infrared sky surveys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservationRegionFor Context triple: [North Ecliptic Pole, isObservationRegionFor, infrared sky surveys]
-
A.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
B.
observesRegion
chosen
Indicates that an entity monitors, watches, or collects information about a specific geographic or spatial region.
-
C.
isObservedIn
Indicates that something (such as a phenomenon, property, or behavior) is detected, recorded, or found to occur within a particular context, setting, or environment.
-
D.
hasObservationArea
Indicates that an entity possesses or includes a designated area from which observations or monitoring activities are conducted.
-
E.
isObservedNear
Indicates that one entity is detected or noticed in close spatial proximity to 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f54ce88190930530958e2a1830 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.