Triple
T25968035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | جزيرة بريم |
E645727
|
entity |
| Predicate | تتبع_إدارياً |
P56871
|
FINISHED |
| Object | اليمن |
—
|
NE NERFINISHED |
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.
followedAdministrativeModelOf
Indicates that one entity adopted or implemented its administrative structure, procedures, or governance framework based on the administrative model used by another entity.
-
B.
administrativelyIn
chosen
Indicates that one entity is located within or belongs to the jurisdiction or governance area of another entity for administrative purposes.
-
C.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
D.
typeOfAdministration
Indicates the specific form or system of administration applied to or governing an entity.
-
E.
administeredBy
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
- 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_69e77e8768648190b27bb578f14bcb88 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604cc423081908edb1fcf694f06fc |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:50 a.m.