Triple
T17980067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dikpalas |
E449576
|
entity |
| Predicate | alternateNumber |
P129987
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Dikpalas, alternateNumber, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateNumber Context triple: [Dikpalas, alternateNumber, 10]
-
A.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
B.
laterNumber
Indicates that one number occurs or is positioned later than another in a specified ordering or sequence.
-
C.
ayahNumber
Indicates the specific verse number assigned to an ayah within a surah or text.
-
D.
alternativeCounting
Indicates that there exists another valid way of counting or enumerating the same set of items or events, distinct from the primary counting method.
-
E.
imoNumber
Indicates that an entity is associated with a specific International Maritime Organization (IMO) identification number used to uniquely identify ships and certain maritime structures.
- 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b202aab88190b44851808c75a848 |
completed | April 19, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.