Triple
T12883246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sewel Convention |
E308156
|
entity |
| Predicate | firstArticulatedInYear |
P1416
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Sewel Convention, firstArticulatedInYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstArticulatedInYear Context triple: [Sewel Convention, firstArticulatedInYear, 1998]
-
A.
firstArticulatedIn
chosen
Indicates the time or context in which something was originally expressed, formulated, or clearly stated for the first time.
-
B.
firstCreationYear
Indicates the year in which something was first created or originally produced.
-
C.
firstPerformanceOfWorkYear
Indicates that the referenced performance is the first time a particular work was performed in a given calendar year.
-
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.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.