Triple
T7050977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bibliothèque publique d’information |
E163762
|
entity |
| Predicate | collectionAccessPolicy |
P53212
|
FINISHED |
| Object | open access |
—
|
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: open access | Statement: [Bibliothèque publique d’information, collectionAccessPolicy, open access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionAccessPolicy Context triple: [Bibliothèque publique d’information, collectionAccessPolicy, open access]
-
A.
collectionPolicy
Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
-
B.
archivesAccessPolicy
chosen
Indicates the rules or conditions governing who can access archives and under what circumstances.
-
C.
collectionTypeAccessed
Indicates that an entity has accessed or interacted with a particular type of collection.
-
D.
collectionRole
Indicates the specific function, responsibility, or position an entity holds within a collection or grouped set of items.
-
E.
collectionRepository
Indicates a relationship where a repository is responsible for storing, managing, or providing access to a collection.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.