Triple
T9743276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gravity Probe B |
E236241
|
entity |
| Predicate | frameDraggingAccuracy |
P62233
|
FINISHED |
| Object | about 19 percent |
—
|
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 19 percent | Statement: [Gravity Probe B, frameDraggingAccuracy, about 19 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameDraggingAccuracy Context triple: [Gravity Probe B, frameDraggingAccuracy, about 19 percent]
-
A.
dragCompensation
Indicates that one entity adjusts or counteracts the drag force experienced by another entity or system.
-
B.
hasAccuracy
chosen
Indicates that something possesses a specified level or measure of correctness, precision, or exactness in relation to a standard or reference.
-
C.
frameDuration
Indicates the length of time that a single frame in a sequence (such as video or animation) is displayed before advancing to the next frame.
-
D.
accuracyDependsOn
Indicates that the accuracy of one entity or process is contingent upon, or influenced by, another entity or factor.
-
E.
parallaxAccuracy
Indicates the degree of precision or reliability associated with a measured parallax value.
- 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.