Triple
T32940046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Revision Committee |
E842641
|
entity |
| Predicate | productPublicationDate |
P31246
|
FINISHED |
| Object | 1901 |
—
|
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: 1901 | Statement: [American Revision Committee, productPublicationDate, 1901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productPublicationDate Context triple: [American Revision Committee, productPublicationDate, 1901]
-
A.
businessReleaseDate
chosen
Indicates the date on which a product, service, or offering is officially made available for business or commercial use.
-
B.
consumerReleaseDate
Indicates the date on which a product or service becomes available for purchase or use by general consumers.
-
C.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
D.
dataReleaseDate
Indicates the date on which a particular dataset or piece of data is officially made available or published.
-
E.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:20 a.m.