Triple
T36595319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benguela Railway |
E902780
|
entity |
| Predicate | completedToBorderWithDRC |
P186059
|
FINISHED |
| Object | 1929 |
—
|
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: 1929 | Statement: [Benguela Railway, completedToBorderWithDRC, 1929]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedToBorderWithDRC Context triple: [Benguela Railway, completedToBorderWithDRC, 1929]
-
A.
designCompletion
Indicates that the design phase of something has been finished or brought to completion.
-
B.
completedWithDam
Indicates that an action, project, or process was completed through the use or involvement of a dam.
-
C.
completedFor
Indicates that one entity has finished or fulfilled a task, process, or obligation on behalf of or in service to another entity.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
boundaryStatus
Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
- F. None of above. chosen
Provenance (4 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_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.