Triple
T29240257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCI network of funeral homes |
E741298
|
entity |
| Predicate | offersPlanningOption |
P5640
|
FINISHED |
| Object | pre‑need funeral contracts |
—
|
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: pre‑need funeral contracts | Statement: [SCI network of funeral homes, offersPlanningOption, pre‑need funeral contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersPlanningOption Context triple: [SCI network of funeral homes, offersPlanningOption, pre‑need funeral contracts]
-
A.
offersPlanType
chosen
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
-
B.
offersProgram
Indicates that an entity provides or makes available a specific program (such as a course, curriculum, or initiative).
-
C.
offersChoiceWith
Indicates that one entity presents or provides an option or alternative in conjunction with another entity, forming a set of choices.
-
D.
offersObject
Indicates that a subject provides or makes available a specific object to another party as an offer.
-
E.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to 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_69f0911dd6fc819097d1abb287016489 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 28, 2026, 12:30 p.m.