Triple
T10612562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartarpur |
E276041
|
entity |
| Predicate | founderOfCommunity |
P8500
|
FINISHED |
| Object | Kartarpur Sikh community |
—
|
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: Kartarpur Sikh community | Statement: [Kartarpur, founderOfCommunity, Kartarpur Sikh community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderOfCommunity Context triple: [Kartarpur, founderOfCommunity, Kartarpur Sikh community]
-
A.
foundedCommunity
chosen
Indicates that an entity established or created a community, organization, or group.
-
B.
founderKnownFor
Indicates that a founder is particularly recognized or notable for a specific work, achievement, product, or contribution.
-
C.
wasFoundedBy
Indicates that an organization, institution, or entity came into existence through the initiating action or establishment by a specific founder or founding group.
-
D.
founderOfMonastery
Indicates that a person established or founded a particular monastery.
-
E.
founder
Indicates that an entity established, created, or started another entity such as an organization, institution, or company.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df5baf94819097b14a73af058f35 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.