Triple
T30408180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Laskaris |
E773535
|
entity |
| Predicate | endedRuleOver |
P161335
|
FINISHED |
| Object | Empire of Nicaea |
—
|
NE NERFINISHED |
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: Empire of Nicaea | Statement: [House of Laskaris, endedRuleOver, Empire of Nicaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedRuleOver Context triple: [House of Laskaris, endedRuleOver, Empire of Nicaea]
-
A.
endedContinuousRuleOf
chosen
Indicates that one entity brought an ongoing rule, regulation, or governing condition applied to another entity to an end.
-
B.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
C.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
D.
expandedUnderRuleOf
Indicates that an entity grew, spread, or increased in scope during the period when another entity (typically a ruler, regime, or governing authority) was in power.
-
E.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68621f9fc81908af56eb9716cbef9 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:04 p.m.