Triple
T25783520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamb Holm |
E649355
|
entity |
| Predicate | hasWarRelatedSite |
P90634
|
FINISHED |
| Object | Italian Chapel |
—
|
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: Italian Chapel | Statement: [Lamb Holm, hasWarRelatedSite, Italian Chapel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWarRelatedSite Context triple: [Lamb Holm, hasWarRelatedSite, Italian Chapel]
-
A.
warRelatedSite
chosen
Indicates a site that is associated with, used in, or significantly affected by a war or armed conflict.
-
B.
hasNearbyMilitaryHistorySite
Indicates that an entity is located close to a site of historical military significance, such as a battlefield, fort, or memorial.
-
C.
associatedWithWar
Indicates a relationship where an entity is connected or related to war, such as by involvement, influence, cause, or context.
-
D.
hasPrimaryTheatreOfWar
Indicates that an armed conflict or military operation is chiefly conducted within a particular geographic theatre or region of war.
-
E.
hasWorldWarIIAssociation
Indicates that there is a notable connection or relevance between an entity and World War II, such as involvement, impact, or contextual association.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 5:52 a.m.