Triple
T4065407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galileo satellite navigation system |
E86311
|
entity |
| Predicate | plannedSatellites |
P53873
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Galileo satellite navigation system, plannedSatellites, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSatellites Context triple: [Galileo satellite navigation system, plannedSatellites, 30]
-
A.
numberOfGEOSatellitesPlanned
Indicates the planned quantity of GEO (geostationary) satellites associated with a given entity or mission.
-
B.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
C.
launchesCommunicationSatellitesOfType
Indicates that an agent initiates the deployment of communication satellites of a specified type into space.
-
D.
numberOfSatellites
Indicates the quantity of satellites that are associated with or orbit a given entity.
-
E.
spaceActivity
Indicates involvement in activities or operations that take place in, or are directly related to, outer space.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefd0995188190b1bc8771fe7f423a |
completed | March 9, 2026, 5:02 p.m. |
Created at: March 9, 2026, 3:38 p.m.