Triple
T25492596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibliothèque publique d’information |
E638872
|
entity |
| Predicate | isNonLendingLibrary |
P160923
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bibliothèque publique d’information, isNonLendingLibrary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonLendingLibrary Context triple: [Bibliothèque publique d’information, isNonLendingLibrary, yes]
-
A.
isLendingLibrary
Indicates that an entity functions as a library that lends items (such as books or media) to users.
-
B.
hasBorrowingSystem
Indicates that an entity possesses or employs a system or mechanism for borrowing items, resources, or services.
-
C.
hasLibraryBranch
Indicates that an entity possesses or is associated with one or more library branches as part of its organizational structure or services.
-
D.
servedByLibrary
Indicates that an entity receives services, resources, or support from a particular library.
-
E.
hasLibraryDistrict
Indicates that an entity is associated with or falls within the jurisdiction of a particular library district.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 21, 2026, 2:39 p.m.