Triple
T10093860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | قسما |
E215812
|
entity |
| Predicate | يُصنّف ضمن |
P24573
|
FINISHED |
| Object | الأناشيد الثورية |
—
|
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: الأناشيد الثورية | Statement: [قسما, يُصنّف ضمن, الأناشيد الثورية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: يُصنّف ضمن Context triple: [قسما, يُصنّف ضمن, الأناشيد الثورية]
-
A.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
B.
classificationIncludes
Indicates that a broader classification category encompasses or contains a specified subclass, member, or element within its scope.
-
C.
isClassifiedUnder
chosen
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
D.
classificationTypeManaged
Indicates that the classification type is controlled or administered through a managed process or system rather than being assigned freely or ad hoc.
-
E.
classificationIntroduced
Indicates that one entity has introduced or established a particular classification or categorization for another entity.
- 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05da3688190b7a1ac8a58e5488f |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.