Triple
T27794879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagenmakersvallei |
E701178
|
entity |
| Predicate | wasLocatedIn |
P40
|
FINISHED |
| Object | Cape Colony |
—
|
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: Cape Colony | Statement: [Wagenmakersvallei, wasLocatedIn, Cape Colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLocatedIn Context triple: [Wagenmakersvallei, wasLocatedIn, Cape Colony]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
formerlyLocatedOn
Indicates that an entity was once located on or situated upon another entity, but is no longer in that position.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
-
E.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6380a86648190b4ef3ee0ce498b12 |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:30 p.m.