Triple
T24775615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernard de Neufmarché |
E619852
|
entity |
| Predicate | ledConquestOf |
P32947
|
FINISHED |
| Object | Brycheiniog |
—
|
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: Brycheiniog | Statement: [Bernard de Neufmarché, ledConquestOf, Brycheiniog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledConquestOf Context triple: [Bernard de Neufmarché, ledConquestOf, Brycheiniog]
-
A.
conquestCampaign
Indicates a military or strategic campaign undertaken with the goal of conquering and taking control of a target entity or territory.
-
B.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
-
C.
typeOfConquest
Indicates the specific manner or category of conquest by which one entity gains control over or dominance of another.
-
D.
attemptedConquest
Indicates that one entity tried, but did not necessarily succeed, to conquer, subjugate, or take control of another entity.
-
E.
conqueredIn
chosen
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410d246ac8190b7c45f6682c16bfb |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:34 a.m.