Triple
T20399061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicare Administrative Contractors |
E500283
|
entity |
| Predicate | usesGuidanceFrom |
P18444
|
FINISHED |
| Object | Medicare manuals |
—
|
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: Medicare manuals | Statement: [Medicare Administrative Contractors, usesGuidanceFrom, Medicare manuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGuidanceFrom Context triple: [Medicare Administrative Contractors, usesGuidanceFrom, Medicare manuals]
-
A.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
usesGuidanceKit
Indicates that one entity employs or relies on a guidance kit to direct, control, or navigate another entity or process.
-
C.
usesGuidelines
Indicates that one entity follows or applies a specified set of guidelines in performing an action or making decisions.
-
D.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
E.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798cf04481909f183c4c75fe6d52 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.