Triple
T29482027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham Naval Memorial |
E747813
|
entity |
| Predicate | worldWarICommemorations |
P11046
|
FINISHED |
| Object | over 8,500 names |
—
|
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: over 8,500 names | Statement: [Chatham Naval Memorial, worldWarICommemorations, over 8,500 names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldWarICommemorations Context triple: [Chatham Naval Memorial, worldWarICommemorations, over 8,500 names]
-
A.
worldWarIRecognition
Indicates formal acknowledgment or commemoration of involvement, service, or impact related to World War I.
-
B.
worldWarIIService
Indicates that an entity served in some capacity during World War II.
-
C.
commemoratesConflict
chosen
Indicates a relationship where something (such as a monument, event, or work) serves to remember, honor, or mark a specific conflict or war.
-
D.
theatreOfWorldWarIIService
Indicates the geographic region or operational area in which an entity participated in military service during World War II.
-
E.
worldWarIReputation
Indicates the reputation or public perception an entity had specifically in relation to World War I.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 28, 2026, 4:04 p.m.