Triple
T9743258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gravity Probe B |
E236241
|
entity |
| Predicate | dataCollectionEnd |
P65789
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Gravity Probe B, dataCollectionEnd, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionEnd Context triple: [Gravity Probe B, dataCollectionEnd, 2005]
-
A.
dataCollectedOn
chosen
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
B.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
-
C.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
D.
dataCollectionLocation
Indicates the place or setting where data is gathered, recorded, or measured.
-
E.
dataCollectionLevel
Indicates the extent or granularity at which data is gathered or recorded within a given context or system.
- 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.