Triple
T4534391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of Nagarpalika |
E106370
|
entity |
| Predicate | typicalFunctions |
P42790
|
FINISHED |
| Object | chairing council meetings |
—
|
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: chairing council meetings | Statement: [President of Nagarpalika, typicalFunctions, chairing council meetings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFunctions Context triple: [President of Nagarpalika, typicalFunctions, chairing council meetings]
-
A.
typicalFunction
chosen
Indicates that something serves as the usual or characteristic function or role of an entity.
-
B.
traditionalFunction
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
-
C.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
D.
typicalTools
Indicates that the related tools are commonly or characteristically used to perform the associated activity, task, or function.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57a2301c8190aa59280a16750156 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:04 p.m.