Triple
T29031471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potchefstroom campus |
E737737
|
entity |
| Predicate | campusStatusWithinUniversity |
P165943
|
FINISHED |
| Object | flagship campus |
—
|
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: flagship campus | Statement: [Potchefstroom campus, campusStatusWithinUniversity, flagship campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campusStatusWithinUniversity Context triple: [Potchefstroom campus, campusStatusWithinUniversity, flagship campus]
-
A.
stateCampus
Indicates that a campus is part of, located within, or administered by a particular state.
-
B.
campusUsedBy
Indicates that a particular campus is utilized or occupied by a specified group, organization, or set of entities.
-
C.
campusState
Indicates the current operational or status condition of a campus (such as open, closed, active, or inactive).
-
D.
hasCampusState
Indicates that an institution’s campus is located within a specified state or state-level administrative region.
-
E.
statusAtUniversity
Indicates the role or standing that an individual holds at a particular university (such as student, faculty, or staff) at a given time.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603a0d14819090b1221d94fc5d66 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 9:55 a.m.