Triple
T3591731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Energy Camera |
E76039
|
entity |
| Predicate | surveyArea |
P44355
|
FINISHED |
| Object | about 5000 square degrees |
—
|
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: about 5000 square degrees | Statement: [Dark Energy Camera, surveyArea, about 5000 square degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surveyArea Context triple: [Dark Energy Camera, surveyArea, about 5000 square degrees]
-
A.
primarySurveyArea
Indicates that a specified area is the main or principal region targeted or covered by a particular survey or data collection activity.
-
B.
surveyCoverage
chosen
Indicates that one entity’s survey or data collection activity extends over, includes, or accounts for another entity or area.
-
C.
surveyMode
Indicates the method or format by which a survey is administered or conducted (e.g., online, phone, in-person).
-
D.
surveyBand
Indicates that an entity conducts or is associated with a survey using a specific observational band or frequency range.
-
E.
surveyType
Indicates the specific category or kind of survey associated with an entity or activity.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.