Triple
T33839775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 subsatellite |
E867326
|
entity |
| Predicate | initialAposelene |
P131949
|
FINISHED |
| Object | ~141 km |
—
|
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: ~141 km | Statement: [Apollo 15 subsatellite, initialAposelene, ~141 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialAposelene Context triple: [Apollo 15 subsatellite, initialAposelene, ~141 km]
-
A.
initialAttitude
Indicates the starting stance, feeling, or disposition one entity holds toward another or toward a situation before any interaction or change occurs.
-
B.
initialPosition
chosen
Indicates the original or starting location of an entity before any movement or change in position occurs.
-
C.
areFirstDiscoveredMoonsOf
Indicates that the related entities are moons that were the first ones discovered orbiting a particular celestial body.
-
D.
initiallyPosesAs
Indicates that one entity first presents itself under a false or alternative identity or role to another entity before its true nature or role is revealed.
-
E.
initialStatus
Indicates the original or starting state assigned to an entity before any changes or updates occur.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:47 a.m.