Triple
T28293259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Hamilton Light Infantry |
E713485
|
entity |
| Predicate | worldWarParticipation |
P60400
|
FINISHED |
| Object | First World War |
—
|
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: First World War | Statement: [Royal Hamilton Light Infantry, worldWarParticipation, First World War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldWarParticipation Context triple: [Royal Hamilton Light Infantry, worldWarParticipation, First World War]
-
A.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
B.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
C.
alliedParticipation
Indicates that one entity takes part in or contributes to an activity, event, or effort in cooperation or alliance with another entity.
-
D.
worldWarIPartOf
Indicates that an event or entity is a component, phase, or subset of World War I.
-
E.
worldWarIService
chosen
Indicates that an entity served or participated in military service during 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 11:30 p.m.