Triple
T24355623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bharatiya Lok Dal |
E613911
|
entity |
| Predicate | strongBaseIn |
P149534
|
FINISHED |
| Object | Uttar Pradesh |
E10722
|
NE 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: Uttar Pradesh | Statement: [Bharatiya Lok Dal, strongBaseIn, Uttar Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongBaseIn Context triple: [Bharatiya Lok Dal, strongBaseIn, Uttar Pradesh]
-
A.
strongBaseExample
chosen
Indicates that the subject is a representative or illustrative instance of a strong base in the given context.
-
B.
strongestIn
Indicates that one entity possesses the greatest strength or power within a specified group, context, or comparison set.
-
C.
weakBaseExample
Indicates that something serves as an illustrative example of a weak base in a chemical or conceptual context.
-
D.
strongerAt
Indicates that one entity has greater strength, power, or effectiveness than another in a specified context, condition, or domain.
-
E.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
- F. None of above.
Provenance (4 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29348b3448190aa0e87c0eb891d66 |
completed | April 29, 2026, 11:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe34945f08190bc0c7146564ff58f |
completed | May 22, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.