Triple
T31479178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mézières |
E803088
|
entity |
| Predicate | statusDuringAncienRegime |
P103516
|
FINISHED |
| Object | royal stronghold |
—
|
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: royal stronghold | Statement: [Mézières, statusDuringAncienRegime, royal stronghold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringAncienRegime Context triple: [Mézières, statusDuringAncienRegime, royal stronghold]
-
A.
functionDuringAncienRegime
Indicates that an entity held or performed a particular official role, duty, or function specifically during the Ancien Régime period.
-
B.
statusBefore1789
chosen
Indicates the status or condition that an entity had prior to the year 1789.
-
C.
legalStatusDuringFrancoRegime
Indicates the legal status or condition an entity held under the laws and policies of the Franco regime in Spain.
-
D.
stanceDuringFrenchRevolution
Indicates the position, attitude, or alignment an entity held regarding the events, factions, or issues of the French Revolution.
-
E.
statusAfter1791
Indicates the condition or standing of an entity as it existed after the year 1791, typically in contrast to its prior status.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 30, 2026, 9:31 p.m.