Triple
T4175432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hollywood Community Plan Area |
E86463
|
entity |
| Predicate | planningScale |
P33672
|
FINISHED |
| Object | sub-city |
—
|
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: sub-city | Statement: [Hollywood Community Plan Area, planningScale, sub-city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planningScale Context triple: [Hollywood Community Plan Area, planningScale, sub-city]
-
A.
hasPlanningLevel
chosen
Indicates that an entity is associated with a specific stage, tier, or granularity within a planning or scheduling hierarchy.
-
B.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
C.
planningModelFor
Indicates that one entity serves as a planning model used to guide, simulate, or structure the planning activities related to another entity.
-
D.
operationScale
Indicates the relative size, scope, or magnitude at which an operation or activity is conducted.
-
E.
isSmallScale
Indicates that the related activity, operation, or entity occurs on a limited or minor scale, involving relatively small size, scope, or capacity.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.