Triple
T28064749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Danville |
E709212
|
entity |
| Predicate | hasPlanningPriority |
P53755
|
FINISHED |
| Object | preservation of small-town character |
—
|
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: preservation of small-town character | Statement: [Town of Danville, hasPlanningPriority, preservation of small-town character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningPriority Context triple: [Town of Danville, hasPlanningPriority, preservation of small-town character]
-
A.
planningPriority
chosen
Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
-
B.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
hasPlanningLevel
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
E.
hasPlanningSignificance
Indicates that something holds importance or relevance for planning, decision-making, or future organizational activities.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: April 27, 2026, 8:42 p.m.