Triple
T369636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distillery District |
E8238
|
entity |
| Predicate | developmentFocus |
P8671
|
FINISHED |
| Object | heritage preservation |
—
|
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: heritage preservation | Statement: [Distillery District, developmentFocus, heritage preservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentFocus Context triple: [Distillery District, developmentFocus, heritage preservation]
-
A.
developedUnder
Indicates that something was created, produced, or brought into existence while being subject to the authority, guidance, or conditions imposed by a particular person, organization, regime, or framework.
-
B.
missionFocus
chosen
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
C.
developsTechnologyFor
Indicates that one entity creates, improves, or engineers technology specifically intended to be used by or to benefit another entity.
-
D.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
E.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.