Triple
T27655022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarya Functional Cargo Block |
E696969
|
entity |
| Predicate | hasSolarArraySpan |
P54107
|
FINISHED |
| Object | about 24.4 m |
—
|
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: about 24.4 m | Statement: [Zarya Functional Cargo Block, hasSolarArraySpan, about 24.4 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolarArraySpan Context triple: [Zarya Functional Cargo Block, hasSolarArraySpan, about 24.4 m]
-
A.
solarArraySpan
chosen
Indicates the total distance or width covered by a solar array, typically measured from one outer edge to the opposite outer edge.
-
B.
solarArray
Indicates that one entity functions as a solar array for another, typically providing solar-generated electrical power or energy.
-
C.
numberOfSolarArrays
Indicates the quantity of solar array units associated with or installed on an entity.
-
D.
solarArrayArea
Indicates the total surface area occupied by a solar array used for collecting solar energy.
-
E.
hasNumberOfHeliostats
Indicates the quantity of heliostats associated with or contained in a given entity.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 2:33 p.m.