Triple
T35158725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baldwin of Toulouse |
E1015199
|
entity |
| Predicate | lordshipHeldIn |
P182343
|
FINISHED |
| Object | region of Toulouse |
—
|
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: region of Toulouse | Statement: [Baldwin of Toulouse, lordshipHeldIn, region of Toulouse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lordshipHeldIn Context triple: [Baldwin of Toulouse, lordshipHeldIn, region of Toulouse]
-
A.
lordshipCreated
Indicates that a lordship was formally established or brought into existence.
-
B.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
C.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
D.
earldomHeldBy
Indicates that a specified earldom is or was held as a title by a particular person or entity.
-
E.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78cf6d1148190881980c8c2ce7b7d |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c337cec8190bfdab225a3cc96db |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4:02 p.m.