Triple
T860171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian National Congress |
E18580
|
entity |
| Predicate | governingLevel |
P5180
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Indian National Congress, governingLevel, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingLevel Context triple: [Indian National Congress, governingLevel, national]
-
A.
levelOfGovernment
Indicates the specific tier or layer within a governmental hierarchy (e.g., local, regional, national) at which an entity operates or an action is taken.
-
B.
governingBodyLevel
chosen
Indicates the hierarchical level or tier at which a governing body operates within a political or organizational structure.
-
C.
jurisdictionLevel
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
D.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
E.
governedFrom
Indicates that an entity exercises governing authority or administrative control over another entity from a specific location or seat of power.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.