Triple
T3148880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Community Development Entity |
E65827
|
entity |
| Predicate | impactFocus |
P8671
|
FINISHED |
| Object | economic revitalization |
—
|
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: economic revitalization | Statement: [Community Development Entity, impactFocus, economic revitalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactFocus Context triple: [Community Development Entity, impactFocus, economic revitalization]
-
A.
missionFocus
chosen
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
B.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
C.
impactBuilding
Indicates that one entity physically collides with or strikes a building, causing an impact event.
-
D.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
E.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5be30fc819097edb620c65055d5 |
completed | March 8, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.