Triple
T38233000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fond du Lac Public Library |
E1013539
|
entity |
| Predicate | hasPublicResource |
P50028
|
FINISHED |
| Object | public meeting spaces |
—
|
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: public meeting spaces | Statement: [Fond du Lac Public Library, hasPublicResource, public meeting spaces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicResource Context triple: [Fond du Lac Public Library, hasPublicResource, public meeting spaces]
-
A.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
B.
hasOnlineResourceType
Indicates that an entity’s associated online resource belongs to a specific type or category (e.g., webpage, dataset, video).
-
C.
hasCommunityResource
chosen
Indicates that an entity provides, contains, or is associated with a resource intended for use by a community.
-
D.
hasMaterialResource
Indicates that an entity possesses, controls, or has access to a tangible material resource.
-
E.
hasResourceBase
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:30 p.m.