Triple
T29196850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pho Hue Street |
E740147
|
entity |
| Predicate | hasTypicalNoiseLevel |
P32166
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Pho Hue Street, hasTypicalNoiseLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalNoiseLevel Context triple: [Pho Hue Street, hasTypicalNoiseLevel, high]
-
A.
hasNoisePerformance
Indicates the degree to which one entity’s operation or behavior produces or is characterized by a certain level or quality of noise.
-
B.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
C.
noiseLevel
chosen
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
D.
noiseCompliance
Indicates that an entity adheres to specified rules or standards governing acceptable noise levels or sound emissions.
-
E.
supportsNoiseChannel
Indicates that one entity is capable of handling, transmitting, or operating with a specified noise channel in a system or process.
- 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_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 12:04 p.m.