Triple
T10451161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium satellite system |
E246425
|
entity |
| Predicate | hasInterSatelliteLinks |
P94107
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Iridium satellite system, hasInterSatelliteLinks, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterSatelliteLinks Context triple: [Iridium satellite system, hasInterSatelliteLinks, yes]
-
A.
numberOfSatellites
Indicates the quantity of satellites that are associated with or orbit a given entity.
-
B.
minimumOperationalSatellites
Indicates the smallest number of satellites required for a system or mission to function at its intended operational capacity.
-
C.
satelliteSystem
Indicates a relationship where one system functions as a satellite or subordinate system orbiting, supporting, or depending on another primary system.
-
D.
hasSatelliteStatus
Indicates that one entity holds the status of being a satellite (e.g., dependent, subordinate, or orbiting body) in relation to another entity.
-
E.
launchesCommunicationSatellitesOfType
Indicates that an agent initiates the deployment of communication satellites of a specified type into 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0a6a548190a54212912f618e4e |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.