Triple
T11038282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Observatory, Greenwich |
E260941
|
entity |
| Predicate | astronomyWorkMovedInYear |
P45630
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [Royal Observatory, Greenwich, astronomyWorkMovedInYear, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomyWorkMovedInYear Context triple: [Royal Observatory, Greenwich, astronomyWorkMovedInYear, 1948]
-
A.
astronomicalAchievement
Indicates an entity has accomplished a notable or significant feat in the field of astronomy or space exploration.
-
B.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
C.
perihelionPassageYear
Indicates the calendar year in which an object passes through, or is predicted to pass through, its perihelion (closest point to the Sun in its orbit).
-
D.
mappedInYear
Indicates that something was mapped or charted during a specific calendar year.
-
E.
movementYear
chosen
Indicates the year in which a movement, relocation, or transfer of an entity took place.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fe93b081909d58bfd4b42715f0 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.