Triple
T348780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem |
E6995
|
entity |
| Predicate | languageSignificantMinority |
P5562
|
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: [Jerusalem, languageSignificantMinority, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSignificantMinority Context triple: [Jerusalem, languageSignificantMinority, Arabic]
-
A.
isOfficialMinorityLanguageIn
Indicates that a language has formal, legally recognized minority-language status within a specified political or geographic entity.
-
B.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
C.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
D.
languageFamilyStatus
Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
-
E.
additionalOfficialLanguage
Indicates that an entity has another language, beyond its primary one, that holds official or formally recognized status.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1dc5f88190b54d084c6def7fc5 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.