Triple
T16358674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian postage stamps |
E397251
|
entity |
| Predicate | collectibleFor |
P123108
|
FINISHED |
| Object | philatelists |
—
|
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: philatelists | Statement: [Georgian postage stamps, collectibleFor, philatelists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectibleFor Context triple: [Georgian postage stamps, collectibleFor, philatelists]
-
A.
collectibleIn
Indicates that one entity can be collected or obtained within the context, location, or container defined by another entity.
-
B.
collectibleAspect
Indicates that one entity represents a collectible-related characteristic, feature, or dimension associated with another entity.
-
C.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
D.
isCollectibleFigure
Indicates that an entity is a figure or model intended primarily for collection rather than ordinary use or play.
-
E.
coinsCollectedFor
Indicates that a certain number of coins has been gathered or accumulated in order to benefit or be used for a particular entity or purpose.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2fad1859c819082b47bf9d7fabd9f |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.