Triple
T28588374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fieschi assassination attempt |
E723571
|
entity |
| Predicate | kingSurvived |
P164477
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fieschi assassination attempt, kingSurvived, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingSurvived Context triple: [Fieschi assassination attempt, kingSurvived, true]
-
A.
wasKingdom
Indicates that one entity functioned as the sovereign kingdom or ruling polity of another entity during a particular period.
-
B.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
-
C.
mostPowerfulKing
Indicates that the subject is the king who holds the greatest power or authority among a specified group of kings.
-
D.
wasKingDuring
Indicates that one entity held the position or title of king throughout the time period associated with another entity.
-
E.
hadKingdom
Indicates that an entity possessed or ruled over a particular kingdom.
- F. None of above. chosen
Provenance (4 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650fb69308190ae8dbe9a897ae7b0 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cb1cf5481908a4fb19b531f52e2 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64d6742a08190b5bd7582fa4f125f |
completed | May 2, 2026, 7:15 p.m. |
Created at: April 28, 2026, 4:19 a.m.