Triple
T15633820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Entry of Christ into Brussels in 1889 |
E375885
|
entity |
| Predicate | titleYearMentioned |
P33319
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [The Entry of Christ into Brussels in 1889, titleYearMentioned, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleYearMentioned Context triple: [The Entry of Christ into Brussels in 1889, titleYearMentioned, 1889]
-
A.
titleYear
Indicates the specific year associated with the release, publication, or official designation of a given title.
-
B.
hasYearInTitle
chosen
Indicates that the title of an entity explicitly contains a year value as part of its text.
-
C.
majorLabelReleaseYear
Indicates the year in which a work (such as an album or single) was released by a major record label.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
yearOfReference
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb7338881909f3c430bb73f91d1 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.