Triple
T38704006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gurdwara management committee |
E950213
|
entity |
| Predicate | typicallySelectedBy |
P381
|
FINISHED |
| Object | election |
—
|
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: election | Statement: [Gurdwara management committee, typicallySelectedBy, election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallySelectedBy Context triple: [Gurdwara management committee, typicallySelectedBy, election]
-
A.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
B.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
C.
selectedTo
Indicates that one entity has been chosen or designated from a set of candidates to perform a role, receive something, or participate in an activity in relation to another entity.
-
D.
areSelectedFor
Indicates that certain entities have been chosen or designated from a larger set for a particular purpose, role, or action.
-
E.
selectionMadeBy
chosen
Indicates that a particular choice or selection was performed or decided by a specific agent or entity.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.