Triple
T21511620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | أمانة العاصمة |
E530737
|
entity |
| Predicate | تتبع_نظام |
P26745
|
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.
trackSystem
Indicates a relationship where one entity monitors, records, or follows the status, behavior, or changes of another entity within a system.
-
B.
followsSystem
chosen
Indicates that one entity adheres to, complies with, or operates according to a particular system, framework, or set of rules defined by another entity.
-
C.
تتبع_عقيدة
Indicates that one entity follows, adheres to, or subscribes to a particular doctrine or creed associated with another entity.
-
D.
track
Indicates that one entity follows, monitors, or keeps a record of another entity’s state, behavior, or progress over time.
-
E.
followsCountingSystemOf
Indicates that one entity uses or adheres to the same counting or numeral system as 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea863b18819080e3ff249b10ec28 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.