Triple
T34516722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château de Beynac |
E886169
|
entity |
| Predicate | opposedFortressAcrossRiver |
P64456
|
FINISHED |
| Object | Château de Castelnaud-la-Chapelle |
—
|
NE NERFINISHED |
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: Château de Castelnaud-la-Chapelle | Statement: [Château de Beynac, opposedFortressAcrossRiver, Château de Castelnaud-la-Chapelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedFortressAcrossRiver Context triple: [Château de Beynac, opposedFortressAcrossRiver, Château de Castelnaud-la-Chapelle]
-
A.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
B.
riverCrossedByAllies
Indicates that the river was traversed or crossed by allied forces.
-
C.
riverDefended
Indicates that a river is actively protected or guarded against threats, such as environmental damage, encroachment, or hostile actions.
-
D.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
E.
acrossWaterFrom
chosen
Indicates that two entities are located on opposite sides of a body of water, separated by that water.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 1, 2026, 2:01 a.m.