Triple
T4916758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marumalarchi Dravida Munnetra Kazhagam |
E110367
|
entity |
| Predicate | hasMassBaseAmong |
P59990
|
FINISHED |
| Object | Tamil population |
—
|
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: Tamil population | Statement: [Marumalarchi Dravida Munnetra Kazhagam, hasMassBaseAmong, Tamil population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMassBaseAmong Context triple: [Marumalarchi Dravida Munnetra Kazhagam, hasMassBaseAmong, Tamil population]
-
A.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
B.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
C.
isMassive
Indicates that one entity has an extremely large size, scale, or extent relative to typical or comparable entities.
-
D.
hasBasedUnit
Indicates that something is defined or measured in terms of a specified base unit.
-
E.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
- F. None of above. chosen
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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa559608190aa8d02b1547b8f97 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.