Triple
T28119756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granada Hills North Neighborhood Council |
E710745
|
entity |
| Predicate | providesInputOn |
P179197
|
FINISHED |
| Object | City services |
—
|
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: City services | Statement: [Granada Hills North Neighborhood Council, providesInputOn, City services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesInputOn Context triple: [Granada Hills North Neighborhood Council, providesInputOn, City services]
-
A.
providesInputFor
chosen
Indicates that one entity supplies data, resources, or material that are used as input by another entity or process.
-
B.
hasInput
Indicates that an entity receives or takes another entity as an input to its process, function, or operation.
-
C.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
D.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
E.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
- 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_69ef9b72f63081909dfbc2c1ddae86c6 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 27, 2026, 9:16 p.m.