Triple
T35608383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PB |
E1028963
|
entity |
| Predicate | denotesCity |
P86374
|
FINISHED |
| Object | Paderborn |
—
|
NE NERFINISHED |
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: Paderborn | Statement: [PB, denotesCity, Paderborn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesCity Context triple: [PB, denotesCity, Paderborn]
-
A.
representsCity
Indicates that one entity serves as the official representative or embodiment of a particular city.
-
B.
namedForCity
Indicates that one entity is named after, or derives its name from, a particular city.
-
C.
isCityOf
Indicates that one entity is a city that belongs to, is located within, or is administratively part of another entity (such as a country, state, or region).
-
D.
refersToCityOn
Indicates that one entity makes reference to, or is specifically about, a particular city located on a given date or temporal context.
-
E.
refersToCityAs
chosen
Indicates that one entity designates, mentions, or identifies another entity specifically as a city.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec80034819090b6ef7a0ffe2d3a |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.