Triple
T38000330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightwood Park |
E948074
|
entity |
| Predicate | followsBuildingPattern |
P47446
|
FINISHED |
| Object | early to mid-20th century rowhouses |
—
|
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: early to mid-20th century rowhouses | Statement: [Brightwood Park, followsBuildingPattern, early to mid-20th century rowhouses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsBuildingPattern Context triple: [Brightwood Park, followsBuildingPattern, early to mid-20th century rowhouses]
-
A.
hasBuildingPattern
chosen
Indicates that an entity exhibits or follows a particular architectural or structural building pattern.
-
B.
followsBuildingCode
Indicates that one entity complies with or adheres to the building code standards established by another governing authority or regulatory framework.
-
C.
followsStructure
Indicates that one entity adheres to, conforms with, or is organized according to the structural pattern defined by another entity.
-
D.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:20 p.m.