Triple
T31455961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conrad of Montferrat |
E802449
|
entity |
| Predicate | assassinationLocation |
P167531
|
FINISHED |
| Object | Tyre |
—
|
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: Tyre | Statement: [Conrad of Montferrat, assassinationLocation, Tyre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assassinationLocation Context triple: [Conrad of Montferrat, assassinationLocation, Tyre]
-
A.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
B.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
C.
wasAssassinatedIn
chosen
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
D.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
-
E.
placeOfKilling
Indicates the location where a killing event took place.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:16 p.m.