Triple
T27706261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Six |
E698566
|
entity |
| Predicate | declaredWhiteGroupAreaUnder |
P63323
|
FINISHED |
| Object | Group Areas Act |
—
|
NE NERFINISHED |
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: Group Areas Act | Statement: [District Six, declaredWhiteGroupAreaUnder, Group Areas Act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaredWhiteGroupAreaUnder Context triple: [District Six, declaredWhiteGroupAreaUnder, Group Areas Act]
-
A.
underliesArea
Indicates that one entity forms the foundational basis or underlying support for a particular area or domain of activity, knowledge, or influence.
-
B.
dateDeclaredGroupArea
Indicates the date on which a specific area was officially designated or declared as a group area.
-
C.
includesAreaOf
Indicates that one entity encompasses or contains the spatial extent or area covered by another entity.
-
D.
regulatedArea
chosen
Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
-
E.
reportingArea
Indicates that one entity serves as the geographic or organizational area for which information, data, or events about another entity are reported or aggregated.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635c7005c8190860c9b01366c286a |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3 p.m.