Triple
T27706273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Six |
E698566
|
entity |
| Predicate | postRemovalCondition |
P104636
|
FINISHED |
| Object | left largely undeveloped for decades |
—
|
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: left largely undeveloped for decades | Statement: [District Six, postRemovalCondition, left largely undeveloped for decades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postRemovalCondition Context triple: [District Six, postRemovalCondition, left largely undeveloped for decades]
-
A.
removalCondition
Indicates the condition or circumstances under which an entity is removed, deleted, or no longer considered applicable.
-
B.
afterRemoval
chosen
Indicates that a condition, state, or relationship holds only once a specified entity or element has been removed.
-
C.
dropCondition
Indicates that an entity ceases to satisfy, or is no longer subject to, a specified condition or requirement.
-
D.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
E.
removal
Indicates the action or process by which something is taken away, eliminated, or detached from something else.
- 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.