Triple
T34516721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Beynac |
E886169
|
entity |
| Predicate | controlledSideDuringHundredYearsWar |
P197862
|
FINISHED |
| Object | French side |
—
|
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 side | Statement: [Château de Beynac, controlledSideDuringHundredYearsWar, French side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledSideDuringHundredYearsWar Context triple: [Château de Beynac, controlledSideDuringHundredYearsWar, French side]
-
A.
controlledByDuringCivilWar
Indicates that one party exercised control or authority over another specifically during a civil war period.
-
B.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
C.
sideInSiegeOfLille
Indicates that an entity participated as a side or belligerent in the Siege of Lille.
-
D.
controlledByAfter1798Battle
Indicates that one entity came under the control or authority of another entity as a result of a battle that took place in or after the year 1798.
-
E.
partOfHistoricalConflict
Indicates that one entity participated in, belonged to, or was involved as a component of a larger historical conflict or war.
- F. None of above. chosen
Provenance (4 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 1, 2026, 2:01 a.m.