Triple
T19770584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohlsdorf Cemetery railway station |
E474873
|
entity |
| Predicate | servesTypeOfPlace |
P6789
|
FINISHED |
| Object | cemetery |
—
|
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: cemetery | Statement: [Ohlsdorf Cemetery railway station, servesTypeOfPlace, cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesTypeOfPlace Context triple: [Ohlsdorf Cemetery railway station, servesTypeOfPlace, cemetery]
-
A.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
isTypicallyServedFor
Indicates that one item is most commonly or customarily served as a meal or course for the other (e.g., a dish typically served for breakfast, lunch, or dinner).
-
C.
isTypicallyServedIn
Indicates that something (such as a food or drink) is most commonly or customarily presented or contained within a particular type of vessel or container.
-
D.
servesVenue
chosen
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535bd8c0819097671783962b6bc5 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.