Triple
T30765156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Mill |
E783346
|
entity |
| Predicate | libraryOperatedBy |
P139735
|
FINISHED |
| Object | Cedar Mill & Bethany Community Libraries association |
—
|
NE NERFINISHED |
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: Cedar Mill & Bethany Community Libraries association | Statement: [Cedar Mill, libraryOperatedBy, Cedar Mill & Bethany Community Libraries association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: libraryOperatedBy Context triple: [Cedar Mill, libraryOperatedBy, Cedar Mill & Bethany Community Libraries association]
-
A.
facilityOperatedBy
Indicates that a facility is managed, run, or controlled by a specified agent or organization.
-
B.
publiclyOperatedBy
Indicates that an entity is managed or run by a public or government organization.
-
C.
operatedByOrganization
chosen
Indicates that an activity, facility, or system is run, managed, or controlled by a specific organization.
-
D.
operatedBookstore
Indicates that one entity managed and ran the day-to-day operations of a bookstore owned or controlled by another entity.
-
E.
marketOperatedBy
Indicates that a market is managed, controlled, or run by a specific operator or organization.
- 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_69f224b047f48190b4f5efeb7ee97b37 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fbcebe081908f256d1f3dea5d34 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.