Triple
T36595337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benguela Railway |
E902780
|
entity |
| Predicate | reopenedForFreight |
P59082
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [Benguela Railway, reopenedForFreight, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedForFreight Context triple: [Benguela Railway, reopenedForFreight, 2010s]
-
A.
reopenedFor
chosen
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
B.
reopenedAsIntermodalHub
Indicates that a previously closed or differently used facility has been reopened and now functions as an intermodal transportation hub integrating multiple modes of transport.
-
C.
continuedFreightOperationsUntil
Indicates that an entity maintained its freight transportation activities up to and including a specified point in time.
-
D.
lineClosedToFreight
Indicates that a railway line is not available for freight services or freight train operations.
-
E.
reopens
Indicates that an entity causes something that was previously closed, stopped, or resolved to be opened, resumed, or reconsidered again.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.