Triple
T1248864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPS |
E26827
|
entity |
| Predicate | subjectToErrorSource |
P1313
|
FINISHED |
| Object | Ionospheric Delay |
—
|
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: Ionospheric Delay | Statement: [GPS, subjectToErrorSource, Ionospheric Delay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectToErrorSource Context triple: [GPS, subjectToErrorSource, Ionospheric Delay]
-
A.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
B.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
C.
criticizesSource
Indicates that one entity expresses disapproval of, or negative judgment about, the content, behavior, or credibility of another entity that is treated as a source.
-
D.
requiresSourceDisclosure
Indicates that performing or using something is contingent on revealing or making known the origin or source from which it was derived.
-
E.
sourceState
Indicates the original or starting state from which a transition, change, or process begins.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf827e088190a16d845cea14f2c9 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.