Triple
T4784946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REGN-EB3 |
E106452
|
entity |
| Predicate | administrationSetting |
P32450
|
FINISHED |
| Object | hospital |
—
|
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: hospital | Statement: [REGN-EB3, administrationSetting, hospital]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrationSetting Context triple: [REGN-EB3, administrationSetting, hospital]
-
A.
administrativeFeature
chosen
Indicates that one entity serves as an administrative or governance-related feature, function, or attribute associated with another entity.
-
B.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
C.
coversAdministration
Indicates that one entity is responsible for managing, overseeing, or handling the administrative aspects of another entity or activity.
-
D.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
E.
defaultNetworkSetting
Indicates that a particular network configuration is the primary or standard setting applied when no other network option is explicitly chosen.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.