Triple
T15182090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallians |
E362769
|
entity |
| Predicate | possibleSuccessorGroups |
P11447
|
FINISHED |
| Object | later Punjabi populations |
—
|
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: later Punjabi populations | Statement: [Mallians, possibleSuccessorGroups, later Punjabi populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleSuccessorGroups Context triple: [Mallians, possibleSuccessorGroups, later Punjabi populations]
-
A.
successorGroups
Indicates that one group is the direct successor or follow-up group to another group in some sequence or lineage.
-
B.
successorCollection
Indicates that one collection directly follows or comes after another collection in an ordered sequence.
-
C.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
D.
eventualSuccessor
chosen
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
E.
numberOfSuccessors
Indicates the count of distinct successor entities directly following a given entity in a sequence or structure.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.