Triple
T10420565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | As-hab al-Maimana |
E245635
|
entity |
| Predicate | groupingType |
P93493
|
FINISHED |
| Object | Hereafter classification |
—
|
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: Hereafter classification | Statement: [As-hab al-Maimana, groupingType, Hereafter classification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupingType Context triple: [As-hab al-Maimana, groupingType, Hereafter classification]
-
A.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
B.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
C.
buttonGrouping
Indicates that multiple buttons are associated together as a single logical or functional group.
-
D.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
E.
areSometimesGroupedWith
Indicates that two or more entities are occasionally but not consistently classified, treated, or considered together as part of the same group.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2bee2081908e5e65df9100d463 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:11 p.m.