Triple
T203532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Bank Note |
E4558
|
entity |
| Predicate | collectibleFeature |
P2370
|
FINISHED |
| Object | variety of issuing banks |
—
|
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: variety of issuing banks | Statement: [National Bank Note, collectibleFeature, variety of issuing banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectibleFeature Context triple: [National Bank Note, collectibleFeature, variety of issuing banks]
-
A.
collectibleAspect
chosen
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
B.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
C.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
D.
featuredIn
Indicates that one entity appears or is prominently included within another entity, such as a person, work, or item being showcased in a larger work, event, or context.
-
E.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.