Triple
T4018465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Douai (1667) |
E91221
|
entity |
| Predicate | combatantControlledAfter |
P16398
|
FINISHED |
| Object | Douai by France |
—
|
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: Douai by France | Statement: [Siege of Douai (1667), combatantControlledAfter, Douai by France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantControlledAfter Context triple: [Siege of Douai (1667), combatantControlledAfter, Douai by France]
-
A.
militaryControl
chosen
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
-
B.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
C.
controlContested
Indicates that authority or dominance over something is disputed or challenged between two or more parties.
-
D.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
-
E.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa984948190a252eaeb9dbae454 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.