Triple
T31479188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mézières |
E803088
|
entity |
| Predicate | fortificationsModified |
P77894
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Mézières, fortificationsModified, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationsModified Context triple: [Mézières, fortificationsModified, 16th century]
-
A.
eraOfFortification
chosen
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
B.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
C.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
D.
fortificationTypeDefended
Indicates the specific type of fortification that an entity is responsible for defending or protecting.
-
E.
fortificationCommanded
Indicates that one entity holds authority over and directs the defense or operation of a particular fortification or fortified structure.
- 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_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:31 p.m.