Triple
T34965624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armadale |
E1008386
|
entity |
| Predicate | firstSerialisationEndYear |
P20837
|
FINISHED |
| Object | 1866 |
—
|
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: 1866 | Statement: [Armadale, firstSerialisationEndYear, 1866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSerialisationEndYear Context triple: [Armadale, firstSerialisationEndYear, 1866]
-
A.
firstSerializationYear
Indicates the year in which an entity (such as a work or series) was first serialized or began its initial serialized publication.
-
B.
firstTypeEndYear
Indicates the year in which the first occurrence or instance of a particular type or category comes to an end.
-
C.
serializationEndYear
chosen
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
D.
firstOngoingSeriesEndYear
Indicates the calendar year in which an entity’s first ongoing series is scheduled or expected to end.
-
E.
yearOfCreationEnd
Indicates the year in which the creation or production of something was completed or came to an end.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.