Triple
T7632928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craigie House, Cambridge, Massachusetts |
E172799
|
entity |
| Predicate | servedAsHeadquartersFrom |
P46909
|
FINISHED |
| Object | July 1775 |
—
|
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: July 1775 | Statement: [Craigie House, Cambridge, Massachusetts, servedAsHeadquartersFrom, July 1775]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHeadquartersFrom Context triple: [Craigie House, Cambridge, Massachusetts, servedAsHeadquartersFrom, July 1775]
-
A.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
B.
headquartersPreviousLocation
Indicates that an entity’s headquarters used to be located at a specified place before moving to its current location.
-
C.
headquartersFoundedAt
Indicates that an organization's headquarters was originally established at a specific location.
-
D.
nearHeadquartersOf
Indicates that one entity is located geographically close to the headquarters of another entity.
-
E.
hasOrHadHeadquartersIn
chosen
Indicates that an organization currently has, or previously had, its main headquarters located in a specified place.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa5f4f08190a7e5259a1b6fb576 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:57 p.m.