Triple
T10663479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point Breeze |
E251287
|
entity |
| Predicate | isUndergoing |
P9472
|
FINISHED |
| Object | redevelopment |
—
|
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: redevelopment | Statement: [Point Breeze, isUndergoing, redevelopment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUndergoing Context triple: [Point Breeze, isUndergoing, redevelopment]
-
A.
undergoing
chosen
Indicates that an entity is currently experiencing, being subjected to, or in the process of a particular action, change, or treatment.
-
B.
isOngoing
Indicates that an action, process, or state is currently in progress and has not yet been completed or concluded.
-
C.
hasOngoing
Indicates that one entity is currently engaged in, experiencing, or maintaining an activity, state, or process that has not yet concluded.
-
D.
oftenUndergo
Indicates that an entity frequently experiences, is subjected to, or passes through a particular process, action, or change.
-
E.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31db6288190857533213fa9f20d |
completed | April 9, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.