Triple
T35729529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trencavel family |
E1032713
|
entity |
| Predicate | lostTerritoriesTo |
P90510
|
FINISHED |
| Object | Simon de Montfort |
—
|
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: Simon de Montfort | Statement: [Trencavel family, lostTerritoriesTo, Simon de Montfort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostTerritoriesTo Context triple: [Trencavel family, lostTerritoriesTo, Simon de Montfort]
-
A.
lostMostTerritoriesBy
Indicates that one entity has lost the greatest number of territories in comparison to others, due to the actions or influence of another entity.
-
B.
lostContinentalTerritory
Indicates that one entity has lost control over part or all of its mainland territorial holdings to another entity or as a result of some event.
-
C.
residualTerritoriesLostBy
Indicates that certain remaining or leftover territories were lost by a specified entity.
-
D.
lostTerritoryBy
chosen
Indicates that one entity has had control or ownership of a territory taken away by another entity.
-
E.
lostMostTerritoriesToBritainBy
Indicates that one entity ceded or lost the greatest amount of its territories to Britain as a result of actions taken by another entity.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.