Triple
T24796645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABC Achrafieh Mall |
E620400
|
entity |
| Predicate | languageUsedOnPremises |
P115774
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [ABC Achrafieh Mall, languageUsedOnPremises, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedOnPremises Context triple: [ABC Achrafieh Mall, languageUsedOnPremises, Arabic]
-
A.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
B.
languageUsedInLocality
chosen
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
C.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
D.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
E.
languageOfProvision
Indicates the language in which a provision, such as a legal or contractual clause, is written or officially expressed.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 4:48 a.m.