Triple
T34824243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cussac-Fort-Médoc |
E1003870
|
entity |
| Predicate | architectOfFort |
P85898
|
FINISHED |
| Object | Sébastien Le Prestre de Vauban |
—
|
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: Sébastien Le Prestre de Vauban | Statement: [Cussac-Fort-Médoc, architectOfFort, Sébastien Le Prestre de Vauban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectOfFort Context triple: [Cussac-Fort-Médoc, architectOfFort, Sébastien Le Prestre de Vauban]
-
A.
architectOfCommissionedBuilding
Indicates that a person served as the architect responsible for designing a building that was specifically commissioned.
-
B.
fortressOriginallyBuiltBy
Indicates that a particular fortress was initially constructed by a specified builder or group.
-
C.
architectOfStructure
chosen
Indicates that an entity is the designer or creator responsible for the architectural design of a particular structure.
-
D.
architectOfMainBuilding
Indicates that one entity is the architect who designed the main building associated with another entity.
-
E.
fortificationEngineer
Indicates a relationship where an entity is responsible for designing, constructing, or maintaining defensive structures or fortifications for another entity or location.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4 p.m.