Triple
T8019511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Observatory |
E186702
|
entity |
| Predicate | documentsTimePeriod |
P56447
|
FINISHED |
| Object | single academic year per volume |
—
|
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: single academic year per volume | Statement: [The Observatory, documentsTimePeriod, single academic year per volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsTimePeriod Context triple: [The Observatory, documentsTimePeriod, single academic year per volume]
-
A.
documentsPeriod
chosen
Indicates that one entity documents, records, or provides written evidence about a specific time period associated with another entity.
-
B.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
E.
collectionTimespan
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8bc90081909f6f5878e6f1f241 |
completed | March 31, 2026, 3:24 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.