Triple
T4065311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariane launch vehicle programme |
E86309
|
entity |
| Predicate | typicalPayloads |
P8440
|
FINISHED |
| Object | communications satellites |
—
|
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: communications satellites | Statement: [Ariane launch vehicle programme, typicalPayloads, communications satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPayloads Context triple: [Ariane launch vehicle programme, typicalPayloads, communications satellites]
-
A.
communicationsPayload
Indicates that an entity carries or contains equipment, data, or components specifically intended for communication purposes.
-
B.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
D.
compatiblePayload
Indicates that one entity can be safely or effectively used as the payload of another entity without conflict or required modification.
-
E.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
- 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_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. |
Created at: March 9, 2026, 3:38 p.m.