Triple
T7536189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bend City Charter |
E178156
|
entity |
| Predicate | isPublicDocument |
P53347
|
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: [Bend City Charter, isPublicDocument, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPublicDocument Context triple: [Bend City Charter, isPublicDocument, true]
-
A.
isPrivateOrPublic
Indicates whether something is designated as private or public in terms of its accessibility or visibility.
-
B.
publicDocument
chosen
Indicates that a document is officially available to the general public without access restrictions.
-
C.
isPublicBodyOf
Indicates that an entity functions as the official public body or authority associated with, responsible for, or governing another entity.
-
D.
isPubliclyAccessible
Indicates that the referenced entity can be accessed or used by the general public without special permissions or restrictions.
-
E.
hasNotableDocument
Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f84c13208190971096a0b81b0ff2 |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.