Triple
T17926139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Name |
E448198
|
entity |
| Predicate | firstSerialisationEndDate |
P86466
|
FINISHED |
| Object | 1863-01-17 |
—
|
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: 1863-01-17 | Statement: [No Name, firstSerialisationEndDate, 1863-01-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSerialisationEndDate Context triple: [No Name, firstSerialisationEndDate, 1863-01-17]
-
A.
firstSerialisedIn
Indicates the original publication or medium in which something (such as a work or story) was first released in serialized form.
-
B.
firstCreationEndDate
Indicates the date on which the initial creation or establishment of something was completed or came to an end.
-
C.
firstPhaseEndDate
chosen
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
D.
firstSerializationYear
Indicates the year in which an entity (such as a work or series) was first serialized or began its initial serialized publication.
-
E.
firstBroadcastEndDate
Indicates the date on which the initial broadcast of something (such as a program or event) concluded.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a54e03588190b36a9bb88e4085de |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.