Triple
T9743273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gravity Probe B |
E236241
|
entity |
| Predicate | confirmedEffect |
P29498
|
FINISHED |
| Object | geodetic effect consistent with general relativity |
—
|
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: geodetic effect consistent with general relativity | Statement: [Gravity Probe B, confirmedEffect, geodetic effect consistent with general relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedEffect Context triple: [Gravity Probe B, confirmedEffect, geodetic effect consistent with general relativity]
-
A.
predictedEffect
Indicates that one entity is expected to cause, influence, or result in a particular outcome or consequence for another entity.
-
B.
measuredEffect
Indicates that an action or process has produced a specific, quantified outcome or impact on something.
-
C.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
D.
hasIntendedEffect
Indicates that one entity is expected or designed to produce a particular effect or outcome on another entity or context.
-
E.
confirmedPredictionOf
chosen
Indicates that a previously made prediction about an entity or event has been verified as accurate or true.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2e5bb081908047e3bf5fe3991c |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.