Triple
T21316501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Strand (XI) |
E525485
|
entity |
| Predicate | collectionPublicationDate |
P30105
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [The Strand (XI), collectionPublicationDate, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectionPublicationDate Context triple: [The Strand (XI), collectionPublicationDate, 1996]
-
A.
hasPublicationDate
chosen
Indicates that an entity is associated with the specific date on which it was published.
-
B.
collectionPublication
Indicates that a collection has been formally published or made publicly available, typically through some publishing process or platform.
-
C.
laterCollectionPublicationYear
Indicates that the referenced collection was published in a year later than the year associated with the compared collection or work.
-
D.
fullPublicationDate
Indicates the complete calendar date on which something is formally published, including day, month, and year.
-
E.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcfdec08190a6e19c907a544921 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:30 p.m.