Triple
T8421994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Brunswick, New Jersey (Johnson & Johnson) |
E198878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate headquarters location |
C400
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: corporate headquarters location Context triple: [New Brunswick, New Jersey (Johnson & Johnson), instanceOf, corporate headquarters location]
-
A.
headquarters
chosen
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
B.
former bank headquarters
A former bank headquarters is a building that once served as the central administrative and operational office of a bank but has since been vacated, repurposed, or reassigned to a different primary use.
-
C.
seat of an international organization
A seat of an international organization is the city or specific location where the organization’s principal headquarters and core administrative functions are permanently established.
-
D.
headquarters agreement
A headquarters agreement is a formal treaty or contract between an international organization and a host state that defines the legal status, privileges, immunities, and operational conditions of the organization’s headquarters within that state.
-
E.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
- F. None of above.
Provenance (1 batch)
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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:06 p.m.