Triple
T27706262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Six |
E698566
|
entity |
| Predicate | dateDeclaredGroupArea |
P162967
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [District Six, dateDeclaredGroupArea, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateDeclaredGroupArea Context triple: [District Six, dateDeclaredGroupArea, 1966]
-
A.
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.
-
B.
areaDefinedAs
Indicates that one area is formally specified, delimited, or characterized in terms of another area or defining criteria.
-
C.
territorialDesignation
Indicates that an entity is assigned, defined, or recognized in terms of a specific geographic or territorial area.
-
D.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
E.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
- 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_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_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 3 p.m.