Triple
T22116849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swartkrans |
E546565
|
entity |
| Predicate | hasSiteCodePrefix |
P147043
|
FINISHED |
| Object | SK |
—
|
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: SK | Statement: [Swartkrans, hasSiteCodePrefix, SK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteCodePrefix Context triple: [Swartkrans, hasSiteCodePrefix, SK]
-
A.
hasSiteCode
Indicates that an entity is associated with a specific site identifier or code used to distinguish its location or facility.
-
B.
hasStationCodePrefix
Indicates that one entity’s station code begins with the prefix specified by the other entity.
-
C.
hasAirportCodePrefix
Indicates that an airport’s code begins with a specified sequence of characters.
-
D.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
E.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1294e85708190b455846bacbdfd03 |
completed | April 28, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:31 p.m.