Triple
T33310104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsavo man-eaters |
E852849
|
entity |
| Predicate | railwayProject |
P39986
|
FINISHED |
| Object | Uganda Railway |
—
|
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: Uganda Railway | Statement: [Tsavo man-eaters, railwayProject, Uganda Railway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayProject Context triple: [Tsavo man-eaters, railwayProject, Uganda Railway]
-
A.
notableRailwayProject
chosen
Indicates that the subject is recognized for involvement in a significant or prominent railway-related project.
-
B.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
-
C.
railwayInfrastructureManager
Indicates that one entity is responsible for managing, maintaining, and operating the railway infrastructure used by another entity.
-
D.
rail
Indicates that one entity criticizes, scolds, or complains vehemently about another entity or situation.
-
E.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:33 a.m.