Triple
T19169119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deira Islands |
E469265
|
entity |
| Predicate | languageUsedInDevelopment |
P58450
|
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: [Deira Islands, languageUsedInDevelopment, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedInDevelopment Context triple: [Deira Islands, languageUsedInDevelopment, Arabic]
-
A.
languagesUsed
chosen
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
B.
developedPrimarilyIn
Indicates that something was mainly created, advanced, or brought into its primary form within a particular context, place, or domain, even if contributions occurred elsewhere.
-
C.
languageOfImplementation
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
D.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
E.
developedForLanguage
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f162ac648190a5f60c6a77b68304 |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.