Triple
T7386152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Danzig (1807) |
E170384
|
entity |
| Predicate | commander |
P1061
|
FINISHED |
| Object | Lefebvre |
E609453
|
NE 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: Lefebvre | Statement: [Siege of Danzig (1807), commander, Lefebvre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lefebvre Context triple: [Siege of Danzig (1807), commander, Lefebvre]
-
A.
Lefebvre
chosen
Lefebvre is a common French surname borne by numerous notable figures in politics, religion, arts, and academia.
-
B.
Lebrun
Lebrun is a French surname borne by various notable figures in politics, arts, and other fields.
-
C.
Giraud
Giraud is a French surname borne by various notable figures in French history and culture.
-
D.
Rabaut Saint-Étienne
Rabaut Saint-Étienne was an 18th-century French Protestant pastor and revolutionary politician who played a significant role in advocating religious tolerance during the French Revolution.
-
E.
Tournier
Tournier is a surname of French origin, sometimes used as a variant of the English surname Turner.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f117ec8190a97cbd0b35d5811a |
completed | March 27, 2026, 9:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802e23714819094a1b31c82a27fee |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:08 p.m.