Triple
T37219432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Washington’s Headquarters |
E922834
|
entity |
| Predicate | periodOfUseAsHeadquarters |
P146693
|
FINISHED |
| Object | 1782–1783 |
—
|
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: 1782–1783 | Statement: [George Washington’s Headquarters, periodOfUseAsHeadquarters, 1782–1783]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfUseAsHeadquarters Context triple: [George Washington’s Headquarters, periodOfUseAsHeadquarters, 1782–1783]
-
A.
usedAsHeadquartersDuringYear
Indicates that a location served as the main headquarters for an entity during a specified year.
-
B.
usedAsHeadquarters
Indicates that a location serves as the main administrative or operational headquarters for an organization or entity.
-
C.
wasHeadquartersDuring
chosen
Indicates that a particular location served as the headquarters of an entity during a specified time period.
-
D.
headquartersCompletionYear
Indicates the year in which an organization's headquarters building was completed.
-
E.
timePeriodAsMainHeadquartersStart
Indicates the point in time when a location first became the main headquarters for an entity.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:15 p.m.