Triple
T27743626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halley’s Comet |
E701919
|
entity |
| Predicate | hasLastPerihelionDate |
P60984
|
FINISHED |
| Object | 1986-02-09 |
—
|
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: 1986-02-09 | Statement: [Halley’s Comet, hasLastPerihelionDate, 1986-02-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLastPerihelionDate Context triple: [Halley’s Comet, hasLastPerihelionDate, 1986-02-09]
-
A.
perihelionDate
chosen
Indicates the date on which an orbiting body reaches its closest point to the Sun in its orbital path.
-
B.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
-
C.
hasAphelionNear
Indicates that one celestial body's aphelion (its farthest point from the object it orbits) lies close to another specified reference point or object.
-
D.
hasPerihelionInside
Indicates that an object's closest point to the Sun (its perihelion) lies within the boundary or interior of another specified region or orbit.
-
E.
hasBrightnessAtPerihelion
Indicates the level of brightness an object exhibits when it is at perihelion, the closest point in its orbit to the body it orbits.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 27, 2026, 4:13 p.m.