Triple
T14323405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellbird campground |
E355149
|
entity |
| Predicate | hasNoiseLevelPolicy |
P74184
|
FINISHED |
| Object | quiet |
—
|
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: quiet | Statement: [Bellbird campground, hasNoiseLevelPolicy, quiet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoiseLevelPolicy Context triple: [Bellbird campground, hasNoiseLevelPolicy, quiet]
-
A.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
B.
hasNoisePerformance
Indicates the degree to which one entity’s operation or behavior produces or is characterized by a certain level or quality of noise.
-
C.
noisePolicy
chosen
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
-
D.
hasNoiseContext
Indicates that an entity is associated with or occurs within a particular noise-related environment or acoustic condition.
-
E.
hasNoiseTerm
Indicates that a given expression, model, or equation includes an additional noise term representing random or unexplained variation.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de883d1de88190a1e2bf2f1b692197 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:13 a.m.