Triple
T24391910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rocroi |
E614914
|
entity |
| Predicate | DucDEnghienLaterTitle |
P156032
|
FINISHED |
| Object | Grand Condé |
E872677
|
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: Grand Condé | Statement: [Battle of Rocroi, DucDEnghienLaterTitle, Grand Condé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DucDEnghienLaterTitle Context triple: [Battle of Rocroi, DucDEnghienLaterTitle, Grand Condé]
-
A.
laterRulerTitle
Indicates that an entity held a particular ruler title at a later point in time, after some earlier status or title.
-
B.
titleInVietnamese
Indicates that one entity is the title of another entity expressed in the Vietnamese language.
-
C.
heldTitleInVietnamese
Indicates that an entity held a specific title or position, expressed in the Vietnamese language.
-
D.
ancientTitle
Indicates that an entity holds or is associated with a title or designation originating from ancient times.
-
E.
titleInKhmer
Indicates that one entity is the title of another entity expressed in the Khmer language.
- F. None of above. chosen
Provenance (5 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_69e2d7e509b88190a53155d4f3de45ce |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294595cec819084cbd5d1b0e08731 |
completed | April 29, 2026, 11:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10b6fca5ec8190b279806d28814da2 |
completed | May 22, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:04 a.m.