Triple
T27176702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourne Library |
E683062
|
entity |
| Predicate | hasInformationScope |
P74565
|
FINISHED |
| Object | local information |
—
|
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: local information | Statement: [Bourne Library, hasInformationScope, local information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformationScope Context triple: [Bourne Library, hasInformationScope, local information]
-
A.
hasRecognitionScope
Indicates the extent or context within which a recognition, award, or acknowledgment is valid or applies.
-
B.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
C.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
D.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
E.
availabilityScope
chosen
Indicates the extent or context within which something is available, accessible, or applicable.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: April 27, 2026, 9:26 a.m.