Triple
T38565856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-1 bus |
E928212
|
entity |
| Predicate | hasPowerSystemType |
P44389
|
FINISHED |
| Object | solar array based power system |
—
|
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: solar array based power system | Statement: [INSAT-1 bus, hasPowerSystemType, solar array based power system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerSystemType Context triple: [INSAT-1 bus, hasPowerSystemType, solar array based power system]
-
A.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
B.
hasTypeOfPowerRegulated
Indicates that one entity exercises a specific kind of power or authority that is subject to regulation or control by another entity or governing framework.
-
C.
hasPowerSupplyType
chosen
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
D.
poweringSystem
Indicates that one entity serves as the source of power or energy that enables the operation or functioning of another entity.
-
E.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: May 3, 2026, 4:32 p.m.