Triple
T34384308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Tigné |
E882516
|
entity |
| Predicate | bastionType |
P30468
|
FINISHED |
| Object | low-profile seaward batteries |
—
|
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: low-profile seaward batteries | Statement: [Fort Tigné, bastionType, low-profile seaward batteries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bastionType Context triple: [Fort Tigné, bastionType, low-profile seaward batteries]
-
A.
hasBastion
Indicates that an entity possesses or is associated with a defensive stronghold or fortified structure (a bastion).
-
B.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
C.
typeOfEnclave
Indicates that one entity is an enclave and specifies the kind or category of enclave it is (e.g., political, cultural, economic).
-
D.
bypassType
Indicates the specific kind or method of bypass used to circumvent or route around a normal process, path, or control.
-
E.
fortType
chosen
Indicates the specific kind or classification of a fort associated with an 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.