Triple
T19894180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Other Foot |
E478105
|
entity |
| Predicate | hasNotableCollectionPublicationYear |
P137735
|
FINISHED |
| Object | 1951 |
—
|
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: 1951 | Statement: [The Other Foot, hasNotableCollectionPublicationYear, 1951]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableCollectionPublicationYear Context triple: [The Other Foot, hasNotableCollectionPublicationYear, 1951]
-
A.
laterCollectionPublicationYear
Indicates that the referenced collection was published in a year later than the year associated with the compared collection or work.
-
B.
notableEditionYear
Indicates the year in which a particular edition of something (such as a work, product, or publication) is considered notable or significant.
-
C.
hasNotablePublicationType
Indicates that an entity is associated with a publication of a specific notable type or category.
-
D.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
E.
folioPublicationYear
Indicates the year in which a particular folio was published.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659105d7481909131d9907ac0094b |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.