Triple
T15966410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GS |
E387202
|
entity |
| Predicate | hasIssuerFoundingYear |
P18715
|
FINISHED |
| Object | 1869 |
—
|
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: 1869 | Statement: [GS, hasIssuerFoundingYear, 1869]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIssuerFoundingYear Context triple: [GS, hasIssuerFoundingYear, 1869]
-
A.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
-
B.
issuerFounded
Indicates that one entity is the organization or person that established or created the other entity at its founding.
-
C.
hasPublisherFounded
Indicates that one entity is the publisher that established or founded the other entity.
-
D.
awardingBodyFoundedIn
chosen
Indicates the year or date when the awarding body (the organization that grants awards) was established or founded.
-
E.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.