Triple
T16934451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kanun |
E410791
|
entity |
| Predicate | stringGrouping |
P124803
|
FINISHED |
| Object | courses of three strings |
—
|
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: courses of three strings | Statement: [kanun, stringGrouping, courses of three strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stringGrouping Context triple: [kanun, stringGrouping, courses of three strings]
-
A.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
B.
letterGroups
Indicates that entities are organized or associated into specific groups based on letters or letter-based criteria.
-
C.
ISOGroupingStatus
Indicates the relationship between an entity and its classification or status within an ISO-defined grouping or category.
-
D.
groupingType
Indicates how multiple entities are categorized or clustered together based on a shared grouping criterion.
-
E.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2899608190a6bacdce9d4ceb84 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.