Triple
T7670916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stodolní Street |
E173743
|
entity |
| Predicate | hasAssociatedIssue |
P29037
|
FINISHED |
| Object | noise complaints |
—
|
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: noise complaints | Statement: [Stodolní Street, hasAssociatedIssue, noise complaints]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedIssue Context triple: [Stodolní Street, hasAssociatedIssue, noise complaints]
-
A.
hasTargetIssue
Indicates that an entity is associated with or directed toward a specific issue, problem, or concern as its focus.
-
B.
hasActivityAtIssue
Indicates that an entity is associated with a specific activity that is currently under consideration, discussion, or dispute.
-
C.
hasInternalIssue
Indicates that an entity is experiencing a problem, fault, or malfunction originating within itself or its internal components or processes.
-
D.
isSubIssueOf
Indicates that one issue is a smaller, dependent, or component part of another, larger parent issue.
-
E.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
- 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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.