Triple
T7357614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Abu Dhabi |
E169664
|
entity |
| Predicate | controls |
P760
|
FINISHED |
| Object | ADQ |
E658824
|
NE 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: ADQ | Statement: [Government of Abu Dhabi, controls, ADQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ADQ Context triple: [Government of Abu Dhabi, controls, ADQ]
-
A.
ADQ
chosen
ADQ is a state-owned investment and holding company of the Emirate of Abu Dhabi that manages a diversified portfolio of strategic assets across key sectors of the economy.
-
B.
ATQ
ATQ is the IATA airport code for Sri Guru Ram Dass Jee International Airport serving Amritsar, India.
-
C.
ANQ
ANQ is the commonly used acronym for the National Assembly of Quebec, the unicameral legislative body of the Canadian province of Quebec.
-
D.
DQI
DQI is the American Physical Society’s Division of Quantum Information, a professional unit focused on advancing research and collaboration in quantum information science.
-
E.
BDQ
BDQ is the IATA airport code for Vadodara Airport in Gujarat, India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f13bf2e881909bc95b93a5664a4f |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802b69cb4819096815b1fac284840 |
completed | March 28, 2026, 4:32 p.m. |
Created at: March 27, 2026, 3:06 p.m.