Triple
T27317202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John IV Laskaris |
E689379
|
entity |
| Predicate | coexistedWithEvent |
P12845
|
FINISHED |
| Object | restoration of the Byzantine Empire in Constantinople in 1261 |
—
|
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: restoration of the Byzantine Empire in Constantinople in 1261 | Statement: [John IV Laskaris, coexistedWithEvent, restoration of the Byzantine Empire in Constantinople in 1261]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coexistedWithEvent Context triple: [John IV Laskaris, coexistedWithEvent, restoration of the Byzantine Empire in Constantinople in 1261]
-
A.
coexistedWith
chosen
Indicates that two entities existed at the same time and in the same context or environment, without implying any specific type of interaction between them.
-
B.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
C.
alsoMetAt
Indicates that the same entities met together at an additional, distinct place or event beyond a previously mentioned meeting location.
-
D.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
-
E.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627e7a7b481908ddd375e2f2f10c8 |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:31 a.m.