Triple
T21434737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pickersgill family |
E528776
|
entity |
| Predicate | locationDuringWar |
P46494
|
FINISHED |
| Object | Baltimore during the War of 1812 |
—
|
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: Baltimore during the War of 1812 | Statement: [Pickersgill family, locationDuringWar, Baltimore during the War of 1812]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationDuringWar Context triple: [Pickersgill family, locationDuringWar, Baltimore during the War of 1812]
-
A.
wartimeLocation
chosen
Indicates the location where an entity is situated or operates during a period of war or armed conflict.
-
B.
locationDuringConflict
Indicates that an entity is situated in a specific place for some or all of the duration of a particular conflict or hostilities.
-
C.
basedInDuringConflict
Indicates that an entity is located or headquartered in a particular place for the duration of a specified conflict or war.
-
D.
postWarLocation
Indicates the place where an entity is located or based after a war or major conflict has ended.
-
E.
stateDuringWar
Indicates that a state or condition exists specifically in the context of, or for the duration of, a war or armed conflict.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b53516d081908f8058a8ee363629 |
completed | April 22, 2026, 11:47 a.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 6 p.m.