Triple
T11784614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franc-Lyonnais |
E280238
|
entity |
| Predicate | hadLocalEstates |
P8997
|
FINISHED |
| Object | provincial estates |
—
|
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: provincial estates | Statement: [Franc-Lyonnais, hadLocalEstates, provincial estates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLocalEstates Context triple: [Franc-Lyonnais, hadLocalEstates, provincial estates]
-
A.
hadEstate
chosen
Indicates that an entity possessed or owned a particular estate or landed property.
-
B.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
C.
originalEstates
Indicates that an entity is associated with or represents the initial or primary estates from which subsequent rights, interests, or derived estates originate.
-
D.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
E.
heldImperialEstate
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a585795c8190aa8a5edf0d99b47f |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.