Triple
T24001125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | مصرف لبنان |
E594249
|
entity |
| Predicate | اللغة_الرسمية_للتعامل |
P33549
|
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.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
B.
languageOfCommunications
chosen
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
D.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
E.
officialLanguageOfListing
Indicates that a specified language is the official language used in a particular listing.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d464f1988190a0a9352c1ec214eb |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:39 p.m.