Triple
T15431445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAe 146 |
E369649
|
entity |
| Predicate | noiseCertification |
P44487
|
FINISHED |
| Object | Stage 3 compliant |
—
|
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: Stage 3 compliant | Statement: [BAe 146, noiseCertification, Stage 3 compliant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noiseCertification Context triple: [BAe 146, noiseCertification, Stage 3 compliant]
-
A.
noiseCompliance
chosen
Indicates that an entity adheres to specified rules or standards governing acceptable noise levels or sound emissions.
-
B.
noiseLevel
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
C.
noisePolicy
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
-
D.
hasNoisePerformance
Indicates the degree to which one entity’s operation or behavior produces or is characterized by a certain level or quality of noise.
-
E.
noiseSource
Indicates that one entity is the origin or producer of a particular noise affecting another entity or the environment.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ed8ea888190bff8dc14859cca31 |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:21 a.m.