Triple
T36486777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikram |
E898953
|
entity |
| Predicate | communicationLossAltitude |
P135008
|
FINISHED |
| Object | about 2.1 km above lunar surface |
—
|
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: about 2.1 km above lunar surface | Statement: [Vikram, communicationLossAltitude, about 2.1 km above lunar surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationLossAltitude Context triple: [Vikram, communicationLossAltitude, about 2.1 km above lunar surface]
-
A.
signalLostAtAltitude
chosen
Indicates that a signal becomes unavailable or is lost when an object reaches a specified altitude.
-
B.
visibilityAltitude
Indicates the altitude at which something becomes visible or can be seen.
-
C.
releaseAltitude
Indicates the altitude at which something is released, such as an object, payload, or substance.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
brokeSoundBarrierAltitude
Indicates the altitude at which an entity broke the sound barrier.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:10 p.m.