Triple
T17643503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brush Park |
E429295
|
entity |
| Predicate | hasRecentDevelopment |
P2224
|
FINISHED |
| Object | townhomes and condominiums |
—
|
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: townhomes and condominiums | Statement: [Brush Park, hasRecentDevelopment, townhomes and condominiums]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecentDevelopment Context triple: [Brush Park, hasRecentDevelopment, townhomes and condominiums]
-
A.
laterDevelopments
Indicates that subsequent events, changes, or outcomes occurred following an earlier situation or state.
-
B.
significantDevelopmentUnder
Indicates that one entity has undergone a major or notable development, change, or advancement under the influence, authority, or conditions provided by another entity.
-
C.
hasDevelopmentStatus
Indicates the current stage or condition of progress or completion that something is in.
-
D.
hasDevelopmentType
chosen
Indicates the type or category of development associated with an entity, such as the nature, form, or stage of its development.
-
E.
hasDevelopmentDimension
Indicates that something possesses or is associated with a particular aspect or dimension of development.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de7055c819080d315bb3637882b |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:03 a.m.