Triple
T6927421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haabʼ |
E160346
|
entity |
| Predicate | isSolar |
P73710
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Haabʼ, isSolar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSolar Context triple: [Haabʼ, isSolar, true]
-
A.
hasMinimumSolarInsolation
Indicates that an entity receives at least a specified minimum amount of solar energy (insolation) over a given area and time period.
-
B.
hasMaximumSolarInsolation
Indicates that an entity receives the highest level of solar radiation or sunlight intensity compared to relevant alternatives or within a given context.
-
C.
hasSolarAngle
Indicates that an entity is associated with a specific angle of incoming solar radiation relative to a reference surface or direction.
-
D.
hasSolarTransition
Indicates a relationship where an entity undergoes or is associated with a change or shift in solar-related conditions, states, or configurations.
-
E.
sunRequirement
Indicates the amount or type of sunlight an entity (such as a plant or object) needs or is designed to receive.
- 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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1bf2088190a8ccfa01d9a1efc5 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d98625c88190a37fdf6d95d7fcbd |
completed | March 27, 2026, 7:24 p.m. |
Created at: March 27, 2026, 2:27 p.m.