Triple
T11258025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highveld Techno Park |
E266489
|
entity |
| Predicate | typicalOccupantType |
P21916
|
FINISHED |
| Object | information technology firms |
—
|
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: information technology firms | Statement: [Highveld Techno Park, typicalOccupantType, information technology firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOccupantType Context triple: [Highveld Techno Park, typicalOccupantType, information technology firms]
-
A.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
-
B.
personType
Indicates that an entity is classified as a particular type or category of person.
-
C.
fieldOfOccupant
chosen
Indicates the specific professional or academic field in which an occupant is engaged or associated.
-
D.
typicalConstituentType
Indicates the usual or characteristic type of component that typically makes up or forms part of something.
-
E.
occupants
Indicates that certain entities are currently inhabiting, residing in, or using a particular place, space, or object.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e935b85c819085e1abf2dd4099c5 |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.