Triple
T24775634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernard de Neufmarché |
E619852
|
entity |
| Predicate | typeOfLordshipEstablished |
P154564
|
FINISHED |
| Object | Marcher lordship |
—
|
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: Marcher lordship | Statement: [Bernard de Neufmarché, typeOfLordshipEstablished, Marcher lordship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLordshipEstablished Context triple: [Bernard de Neufmarché, typeOfLordshipEstablished, Marcher lordship]
-
A.
lordshipCreated
chosen
Indicates that a lordship was formally established or brought into existence.
-
B.
typeOfOverlordship
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
C.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
D.
establishedAsSignoria
Indicates that an entity was instituted or set up as a signoria, i.e., a governing lordship or ruling authority over a city or territory.
-
E.
realmFoundedBy
Indicates that a particular realm or domain was established or created by a specific founding 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:34 a.m.