Triple
T6513810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norco |
E148201
|
entity |
| Predicate | hasLocalOrdinanceFocus |
P16838
|
FINISHED |
| Object | equestrian activities |
—
|
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: equestrian activities | Statement: [Norco, hasLocalOrdinanceFocus, equestrian activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalOrdinanceFocus Context triple: [Norco, hasLocalOrdinanceFocus, equestrian activities]
-
A.
hasLocalOrdinances
chosen
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
B.
hasLocalGovernmentJurisdictionOver
Indicates that one governmental body possesses official authority to administer, regulate, and make binding decisions over a specific geographic area or population.
-
C.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
D.
hasLocalGovernanceType
Indicates the specific form or system of local governance that applies to an entity.
-
E.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f3db330819092503af4fb0649ea |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.