Triple
T30892281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichtenburg |
E786931
|
entity |
| Predicate | warInvolvementContext |
P87038
|
FINISHED |
| Object | Second Anglo-Boer War (1899–1902) |
—
|
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: Second Anglo-Boer War (1899–1902) | Statement: [Lichtenburg, warInvolvementContext, Second Anglo-Boer War (1899–1902)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warInvolvementContext Context triple: [Lichtenburg, warInvolvementContext, Second Anglo-Boer War (1899–1902)]
-
A.
warParticipatedIn
Indicates that an entity took part as a combatant or active participant in a specific war or armed conflict.
-
B.
warTheaterContext
Indicates the broader war or military campaign within which a specific battle, operation, or conflict event takes place.
-
C.
militaryConflictIn
chosen
Indicates that a military conflict takes place within, or is geographically located in, a specified area or region.
-
D.
countryDuringWar
Indicates that a country exists or participates as a relevant actor during a specified war or armed conflict.
-
E.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6923826008190931f5076cd002373 |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:49 p.m.