Triple
T28533336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron Proton Alpha Monitor |
E722097
|
entity |
| Predicate | spacecraftLocation |
P81577
|
FINISHED |
| Object | Sun–Earth L1 Lagrange point |
—
|
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: Sun–Earth L1 Lagrange point | Statement: [Electron Proton Alpha Monitor, spacecraftLocation, Sun–Earth L1 Lagrange point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftLocation Context triple: [Electron Proton Alpha Monitor, spacecraftLocation, Sun–Earth L1 Lagrange point]
-
A.
spacecraftLocated
chosen
Indicates that a spacecraft is situated at, or associated with, a specific location or celestial body.
-
B.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
C.
spacecraftStatus
Indicates the current operational condition or phase of activity a spacecraft is in at a given time.
-
D.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
E.
spacePosition
Indicates the spatial location or coordinates of an entity within a defined space or reference frame.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 3:30 a.m.