Triple
T29857526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTC No. 61 |
E758225
|
entity |
| Predicate | weatherProtection |
P100449
|
FINISHED |
| Object | enclosed in glass pavilion |
—
|
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: enclosed in glass pavilion | Statement: [PTC No. 61, weatherProtection, enclosed in glass pavilion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weatherProtection Context triple: [PTC No. 61, weatherProtection, enclosed in glass pavilion]
-
A.
isWeatherProtected
chosen
Indicates that an entity is shielded from or resistant to adverse weather conditions.
-
B.
weatherConsideration
Indicates that certain conditions, decisions, or actions take into account or are influenced by the current or expected weather.
-
C.
weatherCapability
Indicates that an entity has the ability or functionality to provide, process, or otherwise handle weather-related information or services.
-
D.
skyConditionAdvantage
Indicates that certain sky or weather conditions provide a beneficial effect or favorable advantage to an entity or activity.
-
E.
weatherCondition
Indicates the type of atmospheric state or weather pattern (e.g., sunny, rainy, snowy) affecting a location or time period.
- 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_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:47 p.m.