Triple
T15708788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alamut period |
E380780
|
entity |
| Predicate | startWithEvent |
P89663
|
FINISHED |
| Object | seizure of Alamut fortress by Hasan-i Sabbah |
—
|
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: seizure of Alamut fortress by Hasan-i Sabbah | Statement: [Alamut period, startWithEvent, seizure of Alamut fortress by Hasan-i Sabbah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startWithEvent Context triple: [Alamut period, startWithEvent, seizure of Alamut fortress by Hasan-i Sabbah]
-
A.
significantStartEvent
chosen
Indicates that an event marks an important or defining beginning point for a process, state, or relationship.
-
B.
initialEvents
Indicates that the related events occur at the beginning or starting phase of a process, sequence, or timeline.
-
C.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
D.
allegedStartEvent
Indicates that an entity is claimed or reported (but not confirmed) to be the starting point or initiation of a particular event or process.
-
E.
typeOfEventForStart
Indicates the specific kind or category of event that marks the beginning of something.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.