Triple
T31733442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenland Telescope |
E809921
|
entity |
| Predicate | roleInEHT |
P201195
|
FINISHED |
| Object | extends EHT baseline to the Arctic |
—
|
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: extends EHT baseline to the Arctic | Statement: [Greenland Telescope, roleInEHT, extends EHT baseline to the Arctic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEHT Context triple: [Greenland Telescope, roleInEHT, extends EHT baseline to the Arctic]
-
A.
HeathRole
Indicates a relationship where an entity holds a specific role, function, or position within a health-related context or system.
-
B.
roleInEdom
Indicates that one entity holds or fulfills a specific role, function, or position within the context of Edom.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
roleInAH64
Indicates that an entity has a specific functional role or position in relation to the AH-64 attack helicopter.
-
E.
roleInTSEliotLife
Indicates the specific role, involvement, or significance an entity had in T. S. Eliot’s life.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
| PDg | Predicate description generation | batch_69ffde916fcc81908d6e1b4e6d3f761c |
completed | May 10, 2026, 1:25 a.m. |
Created at: April 30, 2026, 11:22 p.m.