Triple
T34824242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cussac-Fort-Médoc |
E1003870
|
entity |
| Predicate | hasBuildingStartOfFort |
P12643
|
FINISHED |
| Object | late 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: late 17th century | Statement: [Cussac-Fort-Médoc, hasBuildingStartOfFort, late 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBuildingStartOfFort Context triple: [Cussac-Fort-Médoc, hasBuildingStartOfFort, late 17th century]
-
A.
hasFortressConstructed
Indicates that a fortress has been built or established for, by, or at the associated entity.
-
B.
constructionBeganAsFortressIn
chosen
Indicates that the construction of something originally began with the purpose or function of serving as a fortress at a specified time or in a specified place.
-
C.
hasEarlierFortificationPhase
Indicates that one fortification phase chronologically precedes another in the sequence of construction or defensive development.
-
D.
fortificationBuilt
Indicates that a fortification was constructed or established, linking the structure to the event or agent responsible for its building.
-
E.
containsFortress
Indicates that a location or area includes a fortress within its boundaries.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4 p.m.