Triple
T7758534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brouage |
E175958
|
entity |
| Predicate | fortificationsDesignedInCentury |
P77350
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Brouage, fortificationsDesignedInCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortificationsDesignedInCentury Context triple: [Brouage, fortificationsDesignedInCentury, 17th century]
-
A.
fortressWallBuiltInCentury
Indicates that a fortress wall was constructed during a specified century.
-
B.
eraOfFortification
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
C.
eraOfMajorFortification
chosen
Indicates the historical period during which a structure or site underwent its primary or most significant phase of fortification.
-
D.
constructionCentury
Indicates the century during which something was constructed or built.
-
E.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.