Triple
T1473161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of the worlds |
E27180
|
entity |
| Predicate | scopeOfLordship |
P2828
|
FINISHED |
| Object | all times |
—
|
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: all times | Statement: [Lord of the worlds, scopeOfLordship, all times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfLordship Context triple: [Lord of the worlds, scopeOfLordship, all times]
-
A.
regionOfPeerage
Indicates the geographic region or territorial area associated with a particular peerage title or rank.
-
B.
hasViewOfKingdom
Indicates that an entity has a vantage point from which it can see or overlook a kingdom.
-
C.
scopeOfHeraldicAuthority
Indicates the extent or jurisdiction within which a heraldic authority is empowered to grant, regulate, or oversee coats of arms and related heraldic matters.
-
D.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
-
E.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5dc90e481908a4935f266bc7850 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.