Triple
T33218622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riet River |
E850356
|
entity |
| Predicate | wasCrossingPointIn |
P16436
|
FINISHED |
| Object | Second Boer War |
—
|
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: Second Boer War | Statement: [Riet River, wasCrossingPointIn, Second Boer War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCrossingPointIn Context triple: [Riet River, wasCrossingPointIn, Second Boer War]
-
A.
hadCrossingPoints
chosen
Indicates that two entities intersected or overlapped at one or more specific points in space or time.
-
B.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
C.
hasCrossingPoint
Indicates that two or more entities intersect or share at least one common point in space or along their paths.
-
D.
isCrossBetween
Indicates that one entity is a hybrid or intermediate form resulting from the combination or mixing of two other entities.
-
E.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.