Triple
T30877155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A2100-derived GPS III bus |
E786508
|
entity |
| Predicate | designedForConstellation |
P70870
|
FINISHED |
| Object | GPS III |
—
|
NE NERFINISHED |
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: GPS III | Statement: [A2100-derived GPS III bus, designedForConstellation, GPS III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForConstellation Context triple: [A2100-derived GPS III bus, designedForConstellation, GPS III]
-
A.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
B.
supportsConstellation
chosen
Indicates that one entity provides the necessary functionality or compatibility for a specific constellation configuration or system to operate or be used.
-
C.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
D.
relatedConstellation
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
E.
isDistinctiveConstellation
Indicates that a constellation stands out from others due to unique or distinguishing characteristics.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 29, 2026, 8:48 p.m.