Triple
T11803873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anandpur Sahib |
E280694
|
entity |
| Predicate | khalsaFoundedInYear |
P41
|
FINISHED |
| Object | 1699 |
—
|
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: 1699 | Statement: [Anandpur Sahib, khalsaFoundedInYear, 1699]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: khalsaFoundedInYear Context triple: [Anandpur Sahib, khalsaFoundedInYear, 1699]
-
A.
ashramEstablishedFor
Indicates that an ashram was founded or set up specifically for the benefit, use, or purpose of a particular person, group, or cause.
-
B.
foundedOn
chosen
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
-
C.
foundedAt
Indicates the time or date at which an entity (such as an organization, project, or institution) was established or created.
-
D.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
E.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.