Triple
T19157069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRK |
E468952
|
entity |
| Predicate | issuerFoundingYear |
P4025
|
FINISHED |
| Object | 1891 |
—
|
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: 1891 | Statement: [MRK, issuerFoundingYear, 1891]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerFoundingYear Context triple: [MRK, issuerFoundingYear, 1891]
-
A.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
-
B.
foundedAt
chosen
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
C.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
D.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
-
E.
coFoundedInYear
Indicates that two or more entities jointly founded something (such as an organization or company) in a specified year.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb9cf9081908b17073755e83554 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.