Triple
T36486776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vikram |
E898953
|
entity |
| Predicate | communicationLossPhase |
P64517
|
FINISHED |
| Object | final descent |
—
|
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: final descent | Statement: [Vikram, communicationLossPhase, final descent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationLossPhase Context triple: [Vikram, communicationLossPhase, final descent]
-
A.
reasonForContactLoss
Indicates the cause or circumstance that led to the loss or termination of contact between entities.
-
B.
communicationLatency
Indicates the time delay between when a communication is sent by one entity and when it is received or processed by another.
-
C.
communicationEffect
Indicates that one entity’s act of communication causes a change or effect in another entity’s state, behavior, or information.
-
D.
lostDuring
chosen
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
E.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:10 p.m.