Triple
T1274779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Horizons |
E15788
|
entity |
| Predicate | enteredKuiperBelt |
P28278
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [New Horizons, enteredKuiperBelt, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredKuiperBelt Context triple: [New Horizons, enteredKuiperBelt, 2015]
-
A.
recognizedAsDwarfPlanetBy
Indicates that one entity is classified or acknowledged as a dwarf planet by a specified authority, organization, or source.
-
B.
enteredInterstellarSpaceDate
Indicates the date on which an object or entity crossed the boundary of its originating stellar system and entered interstellar space.
-
C.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
-
D.
hasDwarfPlanet
Indicates that one entity possesses or is associated with a dwarf planet as part of its system or domain.
-
E.
hasOrbitalResonanceWith
Indicates that two orbiting bodies have orbital periods in a simple integer ratio, causing their gravitational influences to repeat in a regular, synchronized pattern.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c31400c08190a07ccb736df3bf54 |
completed | March 1, 2026, 10:52 p.m. |
Created at: March 1, 2026, 7:50 p.m.