Triple
T38565872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-1 bus |
E928212
|
entity |
| Predicate | supportsPayloadMassClass |
P206530
|
FINISHED |
| Object | medium-class geostationary payloads |
—
|
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: medium-class geostationary payloads | Statement: [INSAT-1 bus, supportsPayloadMassClass, medium-class geostationary payloads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPayloadMassClass Context triple: [INSAT-1 bus, supportsPayloadMassClass, medium-class geostationary payloads]
-
A.
returnCargoMass
Indicates the mass of cargo that is brought back or returned from a mission, trip, or transport operation.
-
B.
supportsCargoType
Indicates that one entity is capable of handling, transporting, or accommodating a specified type of cargo.
-
C.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
-
D.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
E.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.