Triple
T6495519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alkermes |
E148148
|
entity |
| Predicate | hasOperationalHeadquarters |
P32483
|
FINISHED |
| Object | Waltham, Massachusetts |
—
|
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: Waltham, Massachusetts | Statement: [Alkermes, hasOperationalHeadquarters, Waltham, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOperationalHeadquarters Context triple: [Alkermes, hasOperationalHeadquarters, Waltham, Massachusetts]
-
A.
hasHeadquartersBuilding
Indicates that an organization possesses a specific building that serves as its headquarters location.
-
B.
hasBaseOfOperations
chosen
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
C.
hasHigherHeadquarters
Indicates that one organizational unit serves as the superior or parent headquarters overseeing another unit.
-
D.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
E.
hasOwnerHeadquartersIn
Indicates that the owning entity’s main headquarters is located in the 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_69c009088f3081909cd467b05919de30 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06ab958808190bd85e007e925ffc4 |
completed | March 22, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69c06740bebc81909d9d6956baa2bcb9 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:53 p.m.