Triple
T181365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Health Service |
E3883
|
entity |
| Predicate | serviceCharacteristic |
P274
|
FINISHED |
| Object | comprehensive medical services |
—
|
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: comprehensive medical services | Statement: [National Health Service, serviceCharacteristic, comprehensive medical services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCharacteristic Context triple: [National Health Service, serviceCharacteristic, comprehensive medical services]
-
A.
serviceAreaCharacteristic
Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
-
B.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
C.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
D.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.