Triple
T21027105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zone of Avoidance |
E517966
|
entity |
| Predicate | stillRelevantIn |
P82904
|
FINISHED |
| Object | modern all‑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: modern all‑sky surveys | Statement: [Zone of Avoidance, stillRelevantIn, modern all‑sky surveys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillRelevantIn Context triple: [Zone of Avoidance, stillRelevantIn, modern all‑sky surveys]
-
A.
stillUsedBy
Indicates that something continues to be used or relied upon by another entity at the present time.
-
B.
hasModernRelevance
chosen
Indicates that something maintains significance, applicability, or impact in contemporary times or current contexts.
-
C.
continuedRelevanceAfterEndDate
Indicates that something remains relevant or applicable even after its specified end date has passed.
-
D.
stillInvolvedIn
Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
-
E.
stillMaintained
Indicates that the subject continues to be actively maintained or supported over time.
- 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc7d93908190a2c29a4051fb5acc |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:55 p.m.