Triple
T31409583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman absolutism |
E801223
|
entity |
| Predicate | basedOnOfficeOf |
P11779
|
FINISHED |
| Object | Ottoman sultan |
—
|
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: Ottoman sultan | Statement: [Ottoman absolutism, basedOnOfficeOf, Ottoman sultan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnOfficeOf Context triple: [Ottoman absolutism, basedOnOfficeOf, Ottoman sultan]
-
A.
basisOfOffice
chosen
Indicates the foundational principle, authority, or justification upon which an office or official position is established or exercised.
-
B.
servesAsOfficeOf
Indicates that one entity functions as the official office, headquarters, or administrative base for another entity.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
appliedInOfficeOf
Indicates that an action, application, or process was carried out within or under the authority of a specific office or official institution.
-
E.
builtUnderOfficeOf
Indicates that something was constructed under the authority, supervision, or jurisdiction of a particular office or official body.
- 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 30, 2026, 8:36 p.m.