Triple
T6624390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duc de Duras |
E149757
|
entity |
| Predicate | fateAsBonhommeRichard |
P71586
|
FINISHED |
| Object | sank after battle |
—
|
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: sank after battle | Statement: [Duc de Duras, fateAsBonhommeRichard, sank after battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateAsBonhommeRichard Context triple: [Duc de Duras, fateAsBonhommeRichard, sank after battle]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
faregates
Indicates a relationship where entities are associated with or pass through fare control gates, typically used to regulate and record entry or exit in a transit system.
-
C.
faregatesType
Indicates the type or category of faregates used for access control in a transit or similar system.
-
D.
fleetCommander (British)
Indicates that the subject serves as the fleet commander for the British naval forces.
-
E.
fleetCommander (French)
Indicates that one entity serves as the commanding officer in charge of a fleet associated with another entity.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6bdb76ec48190b59d576170970cc9 |
completed | March 27, 2026, 5:26 p.m. |
Created at: March 27, 2026, 1:58 p.m.