Triple
T7489776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Cambrai (1595) |
E176975
|
entity |
| Predicate | combatantControlAfter |
P21851
|
FINISHED |
| Object | French control of Cambrai |
—
|
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: French control of Cambrai | Statement: [Siege of Cambrai (1595), combatantControlAfter, French control of Cambrai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatantControlAfter Context triple: [Siege of Cambrai (1595), combatantControlAfter, French control of Cambrai]
-
A.
militaryControl
Indicates that one entity exercises authoritative military power, command, or occupation over another entity or territory.
-
B.
controlledAfter
chosen
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
C.
combatant2Commander
Indicates that a combatant serves under the authority or command of a specific commander.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
combatantsIncluded
Indicates that the specified entities are participants or parties involved in a particular combat or conflict.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55abcd481909e42ca857fe46cd1 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.