Triple
T22240336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KER |
E549700
|
entity |
| Predicate | issuerNameChangeYear |
P147510
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [KER, issuerNameChangeYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerNameChangeYear Context triple: [KER, issuerNameChangeYear, 2013]
-
A.
issuerCurrentName
Indicates the current official name by which the issuer is presently identified.
-
B.
issuerMergedInto
Indicates that one issuing entity has been combined into and absorbed by another issuing entity, ceasing to exist as a separate issuer.
-
C.
issuerPreviouslyInstanceOf
Indicates that the current issuer was, at some earlier time, an instance or member of the specified class, type, or category.
-
D.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
E.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
- F. None of above. chosen
Provenance (4 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:38 p.m.