Triple
T26563940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scott C3a (block format) |
E666325
|
entity |
| Predicate | stampIssue |
P160640
|
FINISHED |
| Object | U.S. 24-cent airmail 1918 |
—
|
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: U.S. 24-cent airmail 1918 | Statement: [Scott C3a (block format), stampIssue, U.S. 24-cent airmail 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stampIssue Context triple: [Scott C3a (block format), stampIssue, U.S. 24-cent airmail 1918]
-
A.
stampType
Indicates the specific category or classification of a stamp associated with an entity or transaction.
-
B.
stampSeries
Indicates that one entity is a series or collection of related stamps to which another stamp or stamp issue belongs.
-
C.
stampRequirementFor
Indicates that one entity specifies or imposes a required stamp (e.g., type, presence, or condition of a stamp) that must be satisfied for another entity.
-
D.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
E.
issuedWith
Indicates that one entity is formally provided, granted, or supplied together with another entity as part of the same issuance event.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6149cc0c88190aadaacfa45a2382e |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:54 a.m.