Triple
T36365409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orléans-Longueville line |
E895608
|
entity |
| Predicate | heldFeudalRightsIn |
P182343
|
FINISHED |
| Object | Longueville |
—
|
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: Longueville | Statement: [Orléans-Longueville line, heldFeudalRightsIn, Longueville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldFeudalRightsIn Context triple: [Orléans-Longueville line, heldFeudalRightsIn, Longueville]
-
A.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
B.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
C.
lordshipHeldIn
chosen
Indicates that an entity holds or exercises lordship, authority, or feudal control within a specified place or territorial jurisdiction.
-
D.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
E.
lostFeudalRightsBy
Indicates that one party ceased to hold feudal rights or privileges as a result of actions or circumstances attributable to another party.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.