Triple
T6669888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesundbrunnen locality |
E151699
|
entity |
| Predicate | locatedInFormerBorough |
P72380
|
FINISHED |
| Object | Wedding |
—
|
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: Wedding | Statement: [Gesundbrunnen locality, locatedInFormerBorough, Wedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFormerBorough Context triple: [Gesundbrunnen locality, locatedInFormerBorough, Wedding]
-
A.
locatedInBoroughCommunityDistrict
Indicates that something is situated within a specific borough community district.
-
B.
operatedInBorough
Indicates that an entity conducted its operations or activities within the geographic area of a specific borough.
-
C.
incorporatedAsBorough
Indicates that an entity was formally established and granted legal status as a borough.
-
D.
isBoroughSeatOf
Indicates that a place serves as the administrative center or seat of government for a specific borough.
-
E.
isCentralBoroughOf
Indicates that a borough serves as the primary or central administrative or geographic district of a specified city or region.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6ce72809c8190be85f6e42ca1c8ea |
completed | March 27, 2026, 6:37 p.m. |
Created at: March 27, 2026, 2:02 p.m.