Triple
T11258468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilanesberg National Park |
E266499
|
entity |
| Predicate | fenced |
P49219
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Pilanesberg National Park, fenced, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fenced Context triple: [Pilanesberg National Park, fenced, true]
-
A.
framed
Indicates that one entity has been falsely presented or set up to appear responsible or guilty for an action or situation, typically to mislead others.
-
B.
fences
chosen
Indicates that one entity constructs, installs, or maintains a fence or barrier around or between entities or areas.
-
C.
folded
Indicates that an entity has been bent or doubled over onto itself, typically along a line or crease, changing its original flat or extended form.
-
D.
fielded
Indicates that an entity deployed, presented, or put forward another entity (such as a person, team, or resource) for participation or use in a particular context or activity.
-
E.
frozenIn
Indicates that one entity is immobilized or preserved in a solid, frozen state within or by another entity.
- 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_69d7e936cb048190b4d6fb2851ef8932 |
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.