Triple
T29867413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gbXML |
E758493
|
entity |
| Predicate | supportsWeatherDataLinkage |
P33161
|
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, supportsWeatherDataLinkage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWeatherDataLinkage Context triple: [gbXML, supportsWeatherDataLinkage, true]
-
A.
associatedWithWeather
Indicates a relationship where something is connected or related to weather conditions or phenomena.
-
B.
usesDataLink
Indicates that one entity employs or relies on a data link connection to communicate with or transfer data to another entity.
-
C.
hasWeatherContext
Indicates that something is associated with, influenced by, or described in terms of specific weather conditions or patterns.
-
D.
supportsLinkedData
chosen
Indicates that one entity provides or enables functionality for using, publishing, or interacting with Linked Data associated with another entity.
-
E.
hasWeather
Indicates that a location or environment is experiencing or characterized by a particular type of weather condition.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:52 p.m.