Triple
T5552017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E. J. Pratt Library |
E145548
|
entity |
| Predicate | hasTypeOfUserSpace |
P32186
|
FINISHED |
| Object | reading rooms |
—
|
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: reading rooms | Statement: [E. J. Pratt Library, hasTypeOfUserSpace, reading rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfUserSpace Context triple: [E. J. Pratt Library, hasTypeOfUserSpace, reading rooms]
-
A.
hasSpaceType
chosen
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
B.
hasSubspace
Indicates that one space is a subset or component of another, existing entirely within the larger space.
-
C.
supportsUserType
Indicates that one entity is compatible with, or provides functionality for, a specified type or category of user.
-
D.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
-
E.
hasEnvironmentType
Indicates that an entity is associated with or occurs within a specific type or category of environment.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ff872bc81908e14776f7ba4154e |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:35 p.m.