Triple
T17921373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rail corridor Nuremberg–Berlin |
E448074
|
entity |
| Predicate | partlyUses |
P94810
|
FINISHED |
| Object | high-speed railway sections |
—
|
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: high-speed railway sections | Statement: [rail corridor Nuremberg–Berlin, partlyUses, high-speed railway sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partlyUses Context triple: [rail corridor Nuremberg–Berlin, partlyUses, high-speed railway sections]
-
A.
partOfUse
Indicates that something functions as a component or constituent within the use or application of something else.
-
B.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
C.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
D.
partiallyReusable
Indicates that an entity can be reused to some extent but not fully or indefinitely, implying limited or partial reusability.
-
E.
partlyConsistsOf
chosen
Indicates that one entity is composed in part, but not entirely, 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30a11748190be41361d108aee58 |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.