Triple
T21920662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard College Observatory Annals |
E541301
|
entity |
| Predicate | 20thCenturyContent |
P10303
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Harvard College Observatory Annals, 20thCenturyContent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 20thCenturyContent Context triple: [Harvard College Observatory Annals, 20thCenturyContent, yes]
-
A.
functionDuring20thCentury
Indicates that the function, role, or operation of one entity with respect to another occurred at some time during the 20th century.
-
B.
lostCentury
Indicates that a particular century or era has been forgotten, obscured, or is missing from records or collective knowledge.
-
C.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
D.
century
chosen
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
E.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233af5a481908072c7c928e065ad |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:44 p.m.