Triple
T20357334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaph Hall |
E496683
|
entity |
| Predicate | discoveryYearOfPhobosAndDeimos |
P139812
|
FINISHED |
| Object | 1877 |
—
|
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: 1877 | Statement: [Asaph Hall, discoveryYearOfPhobosAndDeimos, 1877]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryYearOfPhobosAndDeimos Context triple: [Asaph Hall, discoveryYearOfPhobosAndDeimos, 1877]
-
A.
areFirstDiscoveredMoonsOf
Indicates that the related entities are moons that were the first ones discovered orbiting a particular celestial body.
-
B.
hasDiscoveryYearOfCharon
Indicates that an entity has, as its associated value, the calendar year in which Charon was discovered.
-
C.
discoveredBySpacecraft
Indicates that something was first detected, observed, or found as a result of a spacecraft’s instruments or mission activities.
-
D.
discoveryDateOfTitan
Indicates the date on which the celestial body Titan was first discovered or identified.
-
E.
dwarfPlanetRecognitionYear
Indicates the year in which an object was officially recognized or designated as a dwarf planet.
- F. None of above. chosen
Provenance (4 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67854c0448190ab10363f8a218afb |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:25 a.m.