Triple
T35363277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantokrator Monastery |
E1021552
|
entity |
| Predicate | convertedAfterEvent |
P178649
|
FINISHED |
| Object | Fall of Constantinople in 1453 |
—
|
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: Fall of Constantinople in 1453 | Statement: [Pantokrator Monastery, convertedAfterEvent, Fall of Constantinople in 1453]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedAfterEvent Context triple: [Pantokrator Monastery, convertedAfterEvent, Fall of Constantinople in 1453]
-
A.
changesAfterEvents
chosen
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
B.
replacedAfterEvent
Indicates that one entity takes the place of another entity following a specified event or occurrence.
-
C.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
D.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
E.
maintainedAfterEvent
Indicates that a state, condition, or relationship continues to hold true after a specified event has occurred.
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:03 p.m.