Triple
T25910134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Wildenrath |
E652867
|
entity |
| Predicate | railTestCentreOperator |
P32591
|
FINISHED |
| Object | Siemens |
—
|
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: Siemens | Statement: [RAF Wildenrath, railTestCentreOperator, Siemens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTestCentreOperator Context triple: [RAF Wildenrath, railTestCentreOperator, Siemens]
-
A.
trainOperator
Indicates that one entity operates, manages, or runs train services for another entity or within a specific rail system.
-
B.
railwayCentreRunBy
chosen
Indicates that a particular organization or authority is responsible for operating and managing a railway centre.
-
C.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
D.
railwayCompanyTestedOn
Indicates that a railway company has been subjected to a test, evaluation, or assessment in relation to a specified entity or context.
-
E.
trackOperator
Indicates that an entity is responsible for operating, managing, or controlling a particular track or set of tracks.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c450e88190b6bb85debfac30e4 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:28 a.m.