Triple
T33969717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potchefstroom, Transvaal, Union of South Africa |
E870955
|
entity |
| Predicate | nearbyRuralActivity |
P85424
|
FINISHED |
| Object | maize farming region |
—
|
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: maize farming region | Statement: [Potchefstroom, Transvaal, Union of South Africa, nearbyRuralActivity, maize farming region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRuralActivity Context triple: [Potchefstroom, Transvaal, Union of South Africa, nearbyRuralActivity, maize farming region]
-
A.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
B.
nearbyEventDate
Indicates that one event’s date occurs close in time to another event’s date.
-
C.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
-
D.
nearbyActivity
chosen
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
E.
hasRecreationalActivityNearby
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 1, 2026, 1:50 a.m.