Triple
T3511156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holly Springs Community Library |
E74196
|
entity |
| Predicate | providesResourceType |
P3729
|
FINISHED |
| Object | reference materials |
—
|
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: reference materials | Statement: [Holly Springs Community Library, providesResourceType, reference materials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesResourceType Context triple: [Holly Springs Community Library, providesResourceType, reference materials]
-
A.
hasTypeOfResource
chosen
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
B.
includesProviderType
Indicates that one entity’s set of provider types contains or covers the provider type associated with another entity.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
E.
supportsModelType
Indicates that an entity is compatible with, or can operate using, a specified model type.
- 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc0f6cf8819098a1ec8693cc50e7 |
completed | March 8, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69adae0e770481908528fa35eda53003 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.