Triple
T38348619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magdalene College Pepys Library |
E1041614
|
entity |
| Predicate | holdsCollectionOf |
P426
|
FINISHED |
| Object | Samuel Pepys |
—
|
NE NERFINISHED |
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: Samuel Pepys | Statement: [Magdalene College Pepys Library, holdsCollectionOf, Samuel Pepys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsCollectionOf Context triple: [Magdalene College Pepys Library, holdsCollectionOf, Samuel Pepys]
-
A.
isCollectionOf
Indicates that one entity is a group or aggregate composed of multiple instances or elements of another entity.
-
B.
hasCollection
chosen
Indicates that an entity possesses, maintains, or is associated with a set or group of related items treated as a collection.
-
C.
holdsExactlyIn
Indicates that a condition, property, or relationship is true only within a specified context, interval, or scope and not beyond it.
-
D.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
-
E.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
- 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.