Triple
T9743259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gravity Probe B |
E236241
|
entity |
| Predicate | dataAnalysisEnd |
P90457
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Gravity Probe B, dataAnalysisEnd, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataAnalysisEnd Context triple: [Gravity Probe B, dataAnalysisEnd, 2011]
-
A.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
B.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
C.
dataAggregation
Indicates the process by which multiple data points or datasets are combined into a summarized or consolidated form.
-
D.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
E.
usedDataAnalytics
Indicates that an entity applied data analytics techniques or insights in performing an action or making a decision related to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:23 p.m.