Triple
T2518595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Imperial Majesty |
E55469
|
entity |
| Predicate | requiresContext |
P40747
|
FINISHED |
| Object | existence of an empire |
—
|
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: existence of an empire | Statement: [His Imperial Majesty, requiresContext, existence of an empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresContext Context triple: [His Imperial Majesty, requiresContext, existence of an empire]
-
A.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
C.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
-
D.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
E.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:46 p.m.