Triple
T26138099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منف |
E659435
|
entity |
| Predicate | أدرجت_على_قائمة |
P1278
|
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.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
B.
listedOn
chosen
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
-
C.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
D.
includesListedOn
Indicates that one entity contains or references another entity that is recorded or displayed on a specific list or listing.
-
E.
laterIncludedOn
Indicates that one entity was added to, incorporated into, or featured on another entity at a subsequent time.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be1d2408190820365bf7d8436bd |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:18 p.m.