Triple
T5836612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baskerville Virgil |
E129485
|
entity |
| Predicate | hasCollectorInterest |
P51039
|
FINISHED |
| Object | rare book collectors |
—
|
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 book collectors | Statement: [Baskerville Virgil, hasCollectorInterest, rare book collectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectorInterest Context triple: [Baskerville Virgil, hasCollectorInterest, rare book collectors]
-
A.
collectorInterest
chosen
Indicates that one entity has a special interest in acquiring, owning, or seeking out another entity as part of a collection.
-
B.
hasPetInterest
Indicates that one entity has an interest in, affinity for, or concern about pets in relation to another entity or context.
-
C.
significantCollector
Indicates that an entity plays an important or notable role in collecting items, works, or data related to another entity.
-
D.
hasArtCollection
Indicates that an entity possesses, maintains, or is associated with a collection of artworks.
-
E.
canCollect
Indicates that one entity has the ability or permission to gather, receive, or take possession of another entity.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.