Triple
T29196851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pho Hue Street |
E740147
|
entity |
| Predicate | hasTypicalAirQuality |
P122731
|
FINISHED |
| Object | traffic-affected urban air |
—
|
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: traffic-affected urban air | Statement: [Pho Hue Street, hasTypicalAirQuality, traffic-affected urban air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalAirQuality Context triple: [Pho Hue Street, hasTypicalAirQuality, traffic-affected urban air]
-
A.
hasAirQualityMonitoring
Indicates that an entity is equipped with or participates in a system or process for monitoring and measuring air quality.
-
B.
pollutionLevel
Indicates the degree or intensity of environmental contamination present in a given context or location.
-
C.
hasPollutionIssue
Indicates that an entity is affected by, associated with, or characterized by a pollution-related problem or concern.
-
D.
atmosphereStatus
Indicates the current condition or state of an atmosphere, such as its composition, quality, or environmental status.
-
E.
hasEnvironmentalQuality
chosen
Indicates that something possesses a particular environmental characteristic, condition, or attribute.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 12:04 p.m.