Triple
T29867410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gbXML |
E758493
|
entity |
| Predicate | supportsThermalZones |
P207189
|
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: [gbXML, supportsThermalZones, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsThermalZones Context triple: [gbXML, supportsThermalZones, true]
-
A.
hasThermalGroup
Indicates that one entity possesses, includes, or is associated with a specific thermal group (e.g., a set of components or characteristics related to thermal properties or behavior).
-
B.
hasThermalCharacteristic
Indicates that an entity possesses a specific thermal property or behavior, such as conductivity, capacity, or response to temperature.
-
C.
hasThermalResource
Indicates that an entity possesses, provides, or is associated with a source of thermal energy or heat-related capability.
-
D.
hasTemperatureRegime
Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
-
E.
hasNearbyThermalArea
Indicates that one entity is located close to another entity characterized by significant thermal activity, such as hot springs, geysers, or heated ground.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 5:52 p.m.