Triple
T5247660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Magnificent |
E118503
|
entity |
| Predicate | scopeOfReference |
P61710
|
FINISHED |
| Object | reign of Suleiman I |
—
|
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: reign of Suleiman I | Statement: [The Magnificent, scopeOfReference, reign of Suleiman I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfReference Context triple: [The Magnificent, scopeOfReference, reign of Suleiman I]
-
A.
scopeOfDeclaration
Indicates the syntactic region or context within which a particular declaration is valid and can be referenced.
-
B.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
C.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
D.
scopeDefault
Indicates that something applies or is valid in the absence of a more specific or overriding scope.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- F. None of above. chosen
Provenance (4 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b77165c8190bd1ce8a197cef226 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd787975788190848ffbac87896efe |
completed | March 20, 2026, 4:40 p.m. |
Created at: March 20, 2026, 1:50 p.m.