Triple
T32905619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Washington, Pennsylvania |
E841729
|
entity |
| Predicate | encampmentOf |
P63873
|
FINISHED |
| Object | Continental Army |
—
|
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: Continental Army | Statement: [Fort Washington, Pennsylvania, encampmentOf, Continental Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encampmentOf Context triple: [Fort Washington, Pennsylvania, encampmentOf, Continental Army]
-
A.
traditionalEncampmentSide
Indicates the customary or historically established side or position where an encampment is set up relative to another reference point or entity.
-
B.
campLocation
chosen
Indicates the place or area where a camp is set up or located.
-
C.
garrisonOrAssemblyArea
Indicates a location where military forces are stationed, housed, or gathered for organization, preparation, or deployment.
-
D.
hasBivouac
Indicates that an entity provides, contains, or is associated with a temporary camp or bivouac location for use by another entity.
-
E.
oversawWinterEncampment
Indicates that one entity was responsible for supervising, managing, or directing another entity’s activities or conditions during a winter encampment period.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:19 a.m.