Triple
T36613900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1943 Anteros |
E903547
|
entity |
| Predicate | hasCloseApproachesTo |
P13778
|
FINISHED |
| Object | Earth |
—
|
NE NERFINISHED |
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: Earth | Statement: [1943 Anteros, hasCloseApproachesTo, Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCloseApproachesTo Context triple: [1943 Anteros, hasCloseApproachesTo, Earth]
-
A.
hasCloseApproachGeometry
Indicates that there exists detailed geometric information describing the spatial configuration and trajectory of a close approach event between two entities.
-
B.
closestApproachTarget
chosen
Indicates the entity that another entity comes nearest to during its path or motion.
-
C.
closestApproachDistance
Indicates the minimum distance between two entities at the point where they come closest to each other during their motion or interaction.
-
D.
closestApproachDate
Indicates the date on which two entities come nearest to each other in space or position.
-
E.
hasEclipticProximity
Indicates that one celestial object lies close to another in terms of angular separation along or near the ecliptic plane.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:11 p.m.