Triple
T27806595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asiago Astrophysical Observatory |
E702392
|
entity |
| Predicate | hasDataArchive |
P63048
|
FINISHED |
| Object | astronomical observations archive |
—
|
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: astronomical observations archive | Statement: [Asiago Astrophysical Observatory, hasDataArchive, astronomical observations archive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataArchive Context triple: [Asiago Astrophysical Observatory, hasDataArchive, astronomical observations archive]
-
A.
hasNotableArchive
chosen
Indicates that an entity maintains or is associated with an archive that is considered significant or noteworthy.
-
B.
archiveAvailability
Indicates whether something is stored or accessible in an archive, and under what conditions it can be retrieved.
-
C.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
D.
hasDataFile
Indicates that an entity is associated with or linked to a specific data file that stores its related information.
-
E.
hasLongTermDatasetSince
Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 5:39 p.m.