Triple
T31248218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbasid administration |
E796747
|
entity |
| Predicate | centralOrgan |
P71541
|
FINISHED |
| Object | caliphal court in Baghdad |
—
|
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: caliphal court in Baghdad | Statement: [Abbasid administration, centralOrgan, caliphal court in Baghdad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralOrgan Context triple: [Abbasid administration, centralOrgan, caliphal court in Baghdad]
-
A.
centralOrganizationFor
Indicates that one organization serves as the primary or coordinating authority for another organization or group of entities.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
D.
hasCentralOrgan
chosen
Indicates that an entity possesses a primary or main organ that serves as a central functional or structural component.
-
E.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 29, 2026, 9:11 p.m.