Triple
T30966864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French invasion of Fishguard |
E788982
|
entity |
| Predicate | hasPlaceMemorial |
P115845
|
FINISHED |
| Object | Fishguard |
—
|
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: Fishguard | Statement: [French invasion of Fishguard, hasPlaceMemorial, Fishguard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceMemorial Context triple: [French invasion of Fishguard, hasPlaceMemorial, Fishguard]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
memorialSiteFor
chosen
Indicates that a place or structure serves as a dedicated site of remembrance or commemoration for a particular person, group, or event.
-
C.
hasMemorialWall
Indicates that a place or entity includes or is associated with a wall dedicated to commemorating people, events, or memories.
-
D.
hasNearbyMemorials
Indicates that one or more memorials are located in close physical proximity to the referenced entity.
-
E.
hasCommemorativeStructure
Indicates that one entity possesses or is associated with a physical structure created to honor, remember, or commemorate another entity or event.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:54 p.m.