Triple
T11145968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-XL |
E263670
|
entity |
| Predicate | configurationVariantOf |
P64697
|
FINISHED |
| Object | PSLV standard configuration |
—
|
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: PSLV standard configuration | Statement: [PSLV-XL, configurationVariantOf, PSLV standard configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationVariantOf Context triple: [PSLV-XL, configurationVariantOf, PSLV standard configuration]
-
A.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
B.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
C.
governsVariant
Indicates a regulatory relationship where one entity controls, influences, or determines the behavior or state of a specific variant of another entity.
-
D.
productVariant
chosen
Indicates that one entity is a specific variant or version of a more general product entity.
-
E.
serviceVariantOf
Indicates that one service is a variant or alternative version of another, typically differing in configuration, features, or options while serving a similar core function.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.