Triple
T24129516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin–Görlitz railway |
E597903
|
entity |
| Predicate | partiallyUsedBy |
P22634
|
FINISHED |
| Object | Regional-Express services |
—
|
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: Regional-Express services | Statement: [Berlin–Görlitz railway, partiallyUsedBy, Regional-Express services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyUsedBy Context triple: [Berlin–Görlitz railway, partiallyUsedBy, Regional-Express services]
-
A.
areUsedBy
chosen
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
B.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
C.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
D.
partiallySupportedBy
Indicates that something receives incomplete, limited, or not fully sufficient support from another entity.
-
E.
partiallyReusable
Indicates that an entity can be reused to some extent but not fully or indefinitely, implying limited or partial reusability.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7644808190b4bbbf4db1539f48 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:23 p.m.