Triple
T26893329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | মাদ্রাজ |
E677835
|
entity |
| Predicate | ঐতিহাসিক_শাসক |
P8531
|
FINISHED |
| Object | ব্রিটিশ শাসনাধীন শহর |
—
|
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: ব্রিটিশ শাসনাধীন শহর | Statement: [মাদ্রাজ, ঐতিহাসিক_শাসক, ব্রিটিশ শাসনাধীন শহর]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ঐতিহাসিক_শাসক Context triple: [মাদ্রাজ, ঐতিহাসিক_শাসক, ব্রিটিশ শাসনাধীন শহর]
-
A.
historicalRulers
chosen
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
B.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
-
C.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
D.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
E.
historicalHeir
Indicates that one entity is recognized as the successor or inheritor of another in a historical or dynastic context.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:46 a.m.