Triple
T2517241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulawayo Railway Museum |
E55439
|
entity |
| Predicate | hasTypeOfArtifact |
P40733
|
FINISHED |
| Object | tickets and timetables |
—
|
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: tickets and timetables | Statement: [Bulawayo Railway Museum, hasTypeOfArtifact, tickets and timetables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfArtifact Context triple: [Bulawayo Railway Museum, hasTypeOfArtifact, tickets and timetables]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasTypeOfResource
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
C.
hasProjectType
Indicates that an entity is associated with, or classified under, a specific type or category of project.
-
D.
hasMaterialType
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
E.
hasArticulationType
Indicates the specific manner or type of connection or joint by which two parts or entities are linked or articulated.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:46 p.m.