Triple
T5820475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bucentaure |
E129093
|
entity |
| Predicate | surrenderedDate |
P4667
|
FINISHED |
| Object | 21 October 1805 |
—
|
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: 21 October 1805 | Statement: [Bucentaure, surrenderedDate, 21 October 1805]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderedDate Context triple: [Bucentaure, surrenderedDate, 21 October 1805]
-
A.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
B.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
C.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
-
D.
surrenderYear
Indicates the year in which an entity formally surrendered, ending its resistance or hostilities.
-
E.
surrenderEffectiveTime
Indicates the point in time at which a surrender (e.g., of rights, ownership, or an agreement) becomes legally or practically effective.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.