Triple
T499900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu Dhabi |
E10376
|
entity |
| Predicate | playsRole |
P11687
|
FINISHED |
| Object | major political center in the Arab world |
—
|
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: major political center in the Arab world | Statement: [Abu Dhabi, playsRole, major political center in the Arab world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRole Context triple: [Abu Dhabi, playsRole, major political center in the Arab world]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
D.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f13096248190a622a58dcf540b00 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.