Triple
T18016226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVHN |
E431003
|
entity |
| Predicate | hasRealWorldNoise |
P130127
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SVHN, hasRealWorldNoise, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealWorldNoise Context triple: [SVHN, hasRealWorldNoise, true]
-
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.
hasNoiseModes
Indicates that an entity supports or is associated with one or more distinct noise-related operating modes or settings.
-
D.
hasNoiseContext
Indicates that an entity is associated with or occurs within a particular noise-related environment or acoustic condition.
-
E.
hasRealWorldOrigin
Indicates that something is derived from, based on, or directly connected to an actual entity, event, or source in the real world.
- F. None of above. chosen
Provenance (4 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.