Triple
T29622290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 6705 Rockledge Drive |
E755029
|
entity |
| Predicate | corporateOfficeFor |
P48357
|
FINISHED |
| Object | Coventry Health Care |
—
|
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: Coventry Health Care | Statement: [6705 Rockledge Drive, corporateOfficeFor, Coventry Health Care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporateOfficeFor Context triple: [6705 Rockledge Drive, corporateOfficeFor, Coventry Health Care]
-
A.
hasCorporateOffice
chosen
Indicates that an entity maintains a formal corporate office at a specified location or within another organizational entity.
-
B.
currentRepresentativeOffice
Indicates that an entity currently serves as the official representative office for another entity (such as a government, organization, or company).
-
C.
mainOffice
Indicates that one location or office serves as the primary or central office for an organization or entity.
-
D.
headquartersOfBusiness
Indicates that a location serves as the main administrative center or principal office for a business.
-
E.
employerHeadquarters
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e263460819086f937487b3187b2 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:35 p.m.