Triple
T19943582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Write Your Own insurance companies |
E479366
|
entity |
| Predicate | policyCoverage |
P38809
|
FINISHED |
| Object | building coverage |
—
|
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: building coverage | Statement: [Write Your Own insurance companies, policyCoverage, building coverage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyCoverage Context triple: [Write Your Own insurance companies, policyCoverage, building coverage]
-
A.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
B.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
C.
providesCoverage
Indicates that one entity supplies protection, insurance, or service coverage to another entity or for a specified risk or scope.
-
D.
typeOfCoverage
chosen
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
E.
primaryCoverage
Indicates that one entity serves as the main or principal source of coverage (such as insurance or protection) for another 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a64b2788190a49c4ed40aa93b98 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.