Triple
T34515176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradbury, California |
E886129
|
entity |
| Predicate | allowsEquestrianUse |
P192449
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bradbury, California, allowsEquestrianUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsEquestrianUse Context triple: [Bradbury, California, allowsEquestrianUse, true]
-
A.
hasEquestrianFacility
Indicates that a place or property includes facilities specifically designed for horse-related activities, such as riding, training, or boarding.
-
B.
allowsPrivateLand
Indicates that an entity grants permission for privately owned land to be used, accessed, or managed under specified conditions.
-
C.
bicyclesAllowed
Indicates that bicycles are permitted to use or access a particular route, area, or facility.
-
D.
hasRecreationalUseRestriction
Indicates that there is a limitation or prohibition on how an entity may be used for recreational purposes.
-
E.
horseRequirement
Indicates that one entity requires, depends on, or mandates the presence or use of a horse in relation to another entity or activity.
- F. None of above. chosen
Provenance (4 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
| PDg | Predicate description generation | batch_69fd0b92150881909b1166fe6d09aa19 |
completed | May 7, 2026, 10 p.m. |
Created at: May 1, 2026, 2:01 a.m.