Triple
T18180875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Library |
E435276
|
entity |
| Predicate | hasSpecialCollectionsCentre |
P35799
|
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: [New Library, hasSpecialCollectionsCentre, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialCollectionsCentre Context triple: [New Library, hasSpecialCollectionsCentre, yes]
-
A.
hasSpecialCollections
chosen
Indicates that an entity possesses or maintains distinct, curated collections that are set apart from its general holdings.
-
B.
hasHeritageCollections
Indicates that an entity possesses or maintains heritage or historically significant collections.
-
C.
hasMuseumOrTreasureHouse
Indicates that an entity contains, hosts, or is associated with a museum or treasure house.
-
D.
hasMuseumCollectionFocus
Indicates that a museum collection is primarily centered on, dedicated to, or thematically focused around a particular subject, type of object, or area of interest.
-
E.
hasMuseumFunction
Indicates that an entity serves the role or performs the function of a museum.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffa75a081908dad0dcbd736172d |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.