Triple
T445631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Certificate |
E7010
|
entity |
| Predicate | collectingSubtypes |
P13296
|
FINISHED |
| Object | large-size silver certificates |
—
|
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: large-size silver certificates | Statement: [Silver Certificate, collectingSubtypes, large-size silver certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectingSubtypes Context triple: [Silver Certificate, collectingSubtypes, large-size silver certificates]
-
A.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
-
B.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
C.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
-
D.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another entity.
-
E.
nestType
Indicates the type or kind of nest associated with or used by an entity.
- F. None of above. chosen
Provenance (4 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_69a2e7e4676c81909ea0dbdecac0687c |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef479ec08190a659eead6eb0d4d0 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddfb5508190a4e06e1b260d8b2b |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb9e6b0819093863959a6e5730a |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.