Triple
T30408179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Laskaris |
E773535
|
entity |
| Predicate | beganRuleOver |
P86440
|
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, beganRuleOver, Empire of Nicaea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganRuleOver Context triple: [House of Laskaris, beganRuleOver, Empire of Nicaea]
-
A.
beganRule
chosen
Indicates that an entity started its period of ruling or governance over another entity or domain.
-
B.
startOfRule
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
-
C.
coRuleStart
Indicates the point in time or sequence at which two or more rules begin to apply or take effect together.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
- 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_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:04 p.m.