Triple
T16263637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Thani |
E394816
|
entity |
| Predicate | cameToPowerInQatar |
P8145
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Al Thani, cameToPowerInQatar, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameToPowerInQatar Context triple: [Al Thani, cameToPowerInQatar, 19th century]
-
A.
QatarPosition
Indicates a positional or locational relationship involving Qatar, such as where something is situated in or relative to Qatar.
-
B.
cameToPowerIn
chosen
Indicates the time or context in which an entity assumed control, authority, or leadership over a group, organization, or territory.
-
C.
cameToPowerAfter
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
D.
succeededBy as Ruler of Dubai
Indicates that one individual became the next Ruler of Dubai following another individual in that position.
-
E.
cameToPowerThrough
Indicates the manner or process by which an entity attained authority, leadership, or control, specifying how it rose to power.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c672248190a4261be4696d52c5 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.