Triple
T7248644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJBE |
E156538
|
entity |
| Predicate | hasNoiseRestriction |
P74184
|
FINISHED |
| Object | nighttime operations limited |
—
|
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: nighttime operations limited | Statement: [RJBE, hasNoiseRestriction, nighttime operations limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoiseRestriction Context triple: [RJBE, hasNoiseRestriction, nighttime operations limited]
-
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.
hasNoiseTerm
Indicates that a given expression, model, or equation includes an additional noise term representing random or unexplained variation.
-
C.
noiseCompliance
Indicates that an entity adheres to specified rules or standards governing acceptable noise levels or sound emissions.
-
D.
noisePolicy
chosen
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
-
E.
hasNoiseAbatementProcedures
Indicates that specific measures or procedures are in place to reduce or control noise associated with the related entity or activity.
- 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea763f208190af1210cd8d2a05c9 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.