Triple
T17131511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESA ground stations |
E415729
|
entity |
| Predicate | hasAntennaDiameterRange |
P98478
|
FINISHED |
| Object | 13-metre to 35-metre class antennas |
—
|
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: 13-metre to 35-metre class antennas | Statement: [ESA ground stations, hasAntennaDiameterRange, 13-metre to 35-metre class antennas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAntennaDiameterRange Context triple: [ESA ground stations, hasAntennaDiameterRange, 13-metre to 35-metre class antennas]
-
A.
hasExternalAntenna
Indicates that an entity is equipped with or connected to an antenna located outside its main body or enclosure.
-
B.
antennaType
Indicates the specific kind or category of antenna associated with an entity or connection.
-
C.
highGainAntennaDiameter
Indicates the physical diameter measurement of a high-gain antenna associated with an entity.
-
D.
numberOfAntennas
Indicates the quantity of antennas that an entity possesses or is associated with.
-
E.
hasDiameterClass
chosen
Indicates that an entity is associated with a specific category or range based on the size of its diameter.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f02a9fbc81909d820d29417aa55c |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.