Triple
T37852064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Wessels |
E944079
|
entity |
| Predicate | associatedPlaceOfActivity |
P1527
|
FINISHED |
| Object | Johannesburg |
E16031
|
NE 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: Johannesburg | Statement: [Albert Wessels, associatedPlaceOfActivity, Johannesburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPlaceOfActivity Context triple: [Albert Wessels, associatedPlaceOfActivity, Johannesburg]
-
A.
possiblePlaceOfActivity
Indicates that a location is a plausible or candidate site where the referenced entity may carry out or have carried out an activity.
-
B.
placeOfBusinessActivity
Indicates the type or nature of business activity that is conducted at a particular place or location.
-
C.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
-
D.
locationOfWork
chosen
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
E.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
- F. None of above.
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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41542296d88190a57fb0891cb899c5 |
completed | June 28, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.