Triple
T25456707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مكة المكرمة |
E637931
|
entity |
| Predicate | رمز الاتصال الهاتفي |
P134939
|
FINISHED |
| Object | 012 |
—
|
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: 012 | Statement: [مكة المكرمة, رمز الاتصال الهاتفي, 012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: رمز الاتصال الهاتفي Context triple: [مكة المكرمة, رمز الاتصال الهاتفي, 012]
-
A.
codenameNumber
Indicates that an entity is assigned or associated with a specific codename identifier represented as a number.
-
B.
carrierOf
Indicates that one entity serves as the medium, vehicle, or host that contains, transports, or conveys another entity.
-
C.
communicationSymbol
chosen
Indicates a relationship where one entity serves as a symbol or sign used for communication by or between other entities.
-
D.
associatedMob
Indicates a relationship where one entity is linked or connected to a particular mob (mobile entity), typically as its counterpart, partner, or related unit.
-
E.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:10 p.m.