Triple
T3727847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-S |
E78991
|
entity |
| Predicate | rollOffFactor |
P51278
|
FINISHED |
| Object | 0.35 |
—
|
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: 0.35 | Statement: [DVB-S, rollOffFactor, 0.35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rollOffFactor Context triple: [DVB-S, rollOffFactor, 0.35]
-
A.
dragCoefficient
Indicates the dimensionless proportionality factor that relates the drag force experienced by an object moving through a fluid to its shape, flow conditions, and reference area.
-
B.
preservationFactor
Indicates the degree to which something is protected, maintained, or kept intact over time, often moderating how much change, loss, or degradation occurs.
-
C.
pushFactor
Indicates a driving influence or pressure that motivates or forces an entity to move away from, leave, or change its current situation or state.
-
D.
dropHeight
Indicates the vertical distance from which an object is released or allowed to fall.
-
E.
considersFactor
Indicates that one entity takes another entity into account as a factor when forming a judgment, decision, or evaluation.
- F. None of above. chosen
Provenance (4 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf921bc81908bb347d6b9204670 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc226fffc81909c679b44e611fee6 |
completed | March 8, 2026, 6:38 p.m. |
Created at: March 8, 2026, 3:34 p.m.