Triple
T10653008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Orders of South Africa |
E251018
|
entity |
| Predicate | postApartheidDesign |
P1578
|
FINISHED |
| Object | introduced in early 2000s |
—
|
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: introduced in early 2000s | Statement: [National Orders of South Africa, postApartheidDesign, introduced in early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postApartheidDesign Context triple: [National Orders of South Africa, postApartheidDesign, introduced in early 2000s]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
frontDesign
Indicates that one entity serves as the primary or visible front-facing design or appearance of another entity.
-
C.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
D.
designSelectedIn
Indicates that a particular design has been chosen or picked out within a specific context, set, or selection process.
-
E.
designedIn
chosen
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff78ec88190a4d1863fe87245f6 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.