Triple
T19890368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King James Library |
E478012
|
entity |
| Predicate | hasCollectionFeature |
P182
|
FINISHED |
| Object | rare books |
—
|
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: rare books | Statement: [King James Library, hasCollectionFeature, rare books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionFeature Context triple: [King James Library, hasCollectionFeature, rare books]
-
A.
hasCollection
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
B.
hasFeature
chosen
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
hasCollectionAt
Indicates that a collection or gathering of items, data, or resources is located, stored, or maintained at a specific place or context.
-
D.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
E.
hasAdditionalCollection
Indicates that one entity possesses or is associated with an extra or supplementary collection beyond its primary 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590e02388190ab82918750cc2647 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.