Triple
T15255397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emirate of Sharjah |
E364631
|
entity |
| Predicate | emirateNumber |
P16567
|
FINISHED |
| Object | one of seven emirates of the UAE |
—
|
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: one of seven emirates of the UAE | Statement: [Emirate of Sharjah, emirateNumber, one of seven emirates of the UAE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emirateNumber Context triple: [Emirate of Sharjah, emirateNumber, one of seven emirates of the UAE]
-
A.
emirate
Indicates that one entity is an emirate, i.e., a political territory or state ruled by an emir, in relation to another referenced entity.
-
B.
headquartersEmirate
Indicates that an organization or entity has its main headquarters located within a specified emirate.
-
C.
emirateRuled
Indicates that a particular emirate is governed or ruled by a specified ruler or authority.
-
D.
numberOfEmirates
chosen
Indicates the quantitative count of emirates associated with or contained within a given entity.
-
E.
emiratesRepresented
Indicates that one entity serves as an official representative or delegation for the Emirates in relation to another entity or context.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f8cb308190933c4478aa096e24 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.