Triple
T24279614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ektaal |
E605502
|
entity |
| Predicate | hasKhaliVibhagNumber |
P155659
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Ektaal, hasKhaliVibhagNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKhaliVibhagNumber Context triple: [Ektaal, hasKhaliVibhagNumber, 4]
-
A.
hasDesignationNumber
Indicates that an entity is associated with a specific official designation or identification number.
-
B.
hasChamberNumber
Indicates that an entity is associated with a specific chamber identified by a particular number.
-
C.
hasViramaSign
Indicates that a character or script element is associated with, or takes, a virama sign used to suppress the inherent vowel in abugida writing systems.
-
D.
hasDivisionCode
Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
-
E.
hasCouncilAreaCode
Indicates that an entity is associated with a specific council area identified by a particular code.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f51050481908a9bd3c586702057 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.